From: Scott Wood <scottwood@freescale.com>
To: Jia Hongtao-B38951 <B38951@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
David Laight <David.Laight@ACULAB.COM>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Stuart Yoder <b08248@gmail.com>
Subject: Re: [PATCH V4] powerpc/85xx: Add machine check handler to fix PCIe erratum on mpc85xx
Date: Fri, 15 Mar 2013 11:34:52 -0500 [thread overview]
Message-ID: <1363365292.10440.0@snotra> (raw)
In-Reply-To: <412C8208B4A0464FA894C5F0C278CD5D01C18FD6@039-SN1MPN1-003.039d.mgd.msft.net> (from B38951@freescale.com on Thu Mar 14 21:47:58 2013)
On 03/14/2013 09:47:58 PM, Jia Hongtao-B38951 wrote:
>=20
> > -----Original Message-----
> > From: Wood Scott-B07421
> > Sent: Thursday, March 14, 2013 12:38 AM
> > To: David Laight
> > Cc: Jia Hongtao-B38951; Wood Scott-B07421; =20
> linuxppc-dev@lists.ozlabs.org;
> > Stuart Yoder
> > Subject: Re: [PATCH V4] powerpc/85xx: Add machine check handler to =20
> fix
> > PCIe erratum on mpc85xx
> >
> > On 03/13/2013 04:40:40 AM, David Laight wrote:
> > > > 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
>=20
> 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 =20
> back.
> probe_kernel_address() also have the same issue.
That's not the point -- the point is to let the page fault handler know =20
that it should go directly to bad_page_fault(). Do not pass =20
handle_mm_fault(). Do not collect a page from disk.
Granted, we're already in atomic context which will have that effect =20
due to being in the machine check handler, but it's better to be =20
explicit about it and not depend on how pagefault_diasble() is =20
implemented.
-Scott=
next prev parent reply other threads:[~2013-03-15 16:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 8:40 [PATCH V4] powerpc/85xx: Add machine check handler to fix PCIe erratum on mpc85xx Jia Hongtao
2013-03-04 16:16 ` Stuart Yoder
2013-03-04 23:45 ` Scott Wood
2013-03-05 10:12 ` Jia Hongtao-B38951
2013-03-05 18:47 ` Scott Wood
2013-03-06 8:28 ` Jia Hongtao-B38951
2013-03-06 10:24 ` David Laight
2013-03-07 8:06 ` Jia Hongtao-B38951
2013-03-07 10:04 ` David Laight
2013-03-07 16:37 ` Scott Wood
2013-03-08 8:01 ` Jia Hongtao-B38951
2013-03-09 0:49 ` Scott Wood
2013-03-12 7:40 ` Jia Hongtao-B38951
2013-03-12 9:47 ` David Laight
2013-03-12 21:24 ` Scott Wood
2013-03-13 9:40 ` David Laight
2013-03-13 16:37 ` Scott Wood
2013-03-15 2:47 ` Jia Hongtao-B38951
2013-03-15 16:34 ` Scott Wood [this message]
2013-03-29 8:03 ` Jia Hongtao-B38951
2013-03-29 16:33 ` Scott Wood
2013-04-02 9:28 ` Jia Hongtao-B38951
2013-04-02 19:46 ` Scott Wood
2013-03-04 17:15 ` David Laight
2013-03-05 10:12 ` Jia Hongtao-B38951
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1363365292.10440.0@snotra \
--to=scottwood@freescale.com \
--cc=B07421@freescale.com \
--cc=B38951@freescale.com \
--cc=David.Laight@ACULAB.COM \
--cc=b08248@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).