Thread (25 messages) 25 messages, 4 authors, 2013-04-02

RE: [PATCH V4] powerpc/85xx: Add machine check handler to fix PCIe erratum on mpc85xx

From: Jia Hongtao-B38951 <hidden>
Date: 2013-03-29 08:04:01

-----Original Message-----
From: Wood Scott-B07421
Sent: Saturday, March 16, 2013 12:35 AM
To: Jia Hongtao-B38951
Cc: Wood Scott-B07421; David Laight; linuxppc-dev@lists.ozlabs.org;
Stuart Yoder
Subject: Re: [PATCH V4] powerpc/85xx: Add machine check handler to fix
PCIe erratum on mpc85xx
=20
On 03/14/2013 09:47:58 PM, Jia Hongtao-B38951 wrote:
quoted
quoted
-----Original Message-----
From: Wood Scott-B07421
Sent: Thursday, March 14, 2013 12:38 AM
To: David Laight
Cc: Jia Hongtao-B38951; Wood Scott-B07421;
linuxppc-dev@lists.ozlabs.org;
quoted
Stuart Yoder
Subject: Re: [PATCH V4] powerpc/85xx: Add machine check handler to
fix
quoted
PCIe erratum on mpc85xx

On 03/13/2013 04:40:40 AM, David Laight wrote:
quoted
quoted
Hmm, seems there's no probe_user_address() -- for userspace we
basically want the same thing minus the KERNEL_DS.  See
arch/powerpc/perf/callchain.c for an example.
Isn't that just copy_from_user() ?
Plus pagefault_disable/enable().

-Scott
pagefault_disable() is identical to preempt_disable(). So I think this
could not avoid other cpu to swap out the instruction we want to read
back.
probe_kernel_address() also have the same issue.
=20
That's not the point -- the point is to let the page fault handler know
that it should go directly to bad_page_fault().  Do not pass
handle_mm_fault().  Do not collect a page from disk.
=20
Granted, we're already in atomic context which will have that effect
due to being in the machine check handler, but it's better to be
explicit about it and not depend on how pagefault_diasble() is
implemented.
=20
-Scott

Based on the comments I updated the machine check handler.

Changes from last version:
* Check MSR_GS state
* Check if the instruction is LD
* Handle the user space issue

The updated machine check handler is as following:

int fsl_pci_mcheck_exception(struct pt_regs *regs)
{
        unsigned int op, rd;
        u32 inst;
        int ret;
        phys_addr_t addr =3D 0;

        /* Let KVM/QEMU deal with the exception */
        if (regs->msr & MSR_GS)
                return 0;

#ifdef CONFIG_PHYS_64BIT
        addr =3D mfspr(SPRN_MCARU);
        addr <<=3D 32;
#endif
        addr +=3D mfspr(SPRN_MCAR);

        if (is_in_pci_mem_space(addr)) {
                if (user_mode(regs)) {
                        pagefault_disable();
                        ret =3D copy_from_user(&(inst), (u32 __user *)regs-=
nip, sizeof(inst));
                        pagefault_enable();
                } else {
                        ret =3D probe_kernel_address(regs->nip, inst);
                }

                op =3D get_op(inst);
                /* Check if the instruction is LD */
                if (!ret && (op =3D=3D 111010)) {
                        rd =3D get_rt(inst);
                        regs->gpr[rd] =3D 0xffffffff;
                }

                regs->nip +=3D 4;
                return 1;
        }

        return 0;
}

BTW, I'm still not sure how to deal with LD instruction with update.

Any comments and suggestions are welcomed.

Thanks.
-Hongtao.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help