From: Jon Loeliger <jdl@freescale.com>
To: Paul Mackerras <paulus@samba.org>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH] Treat ISI faults as read faults on classic 32-bit PowerPC
Date: Thu, 19 Jul 2007 11:44:57 -0500 [thread overview]
Message-ID: <1184863497.16820.8.camel@ld0161-tx32> (raw)
In-Reply-To: <18078.43412.493174.590540@cargo.ozlabs.ibm.com>
On Wed, 2007-07-18 at 19:00, Paul Mackerras wrote:
> Hmmm. The dangling else clauses are pretty gross, and in fact we have
> the same problem on POWER3 and RS64 processors (to be fair, we had
> the problem before and didn't notice, but we should still fix it).
>
> How about this instead? Could people test it please? (Note that
> CPU_FTR_NOEXECUTE is 0 in 32-bit kernels.)
>
> Paul.
>
> diff --git a/arch/powerpc/mm/fault.c b/arch/powerpc/mm/fault.c
> index 0ece513..99c3093 100644
> --- a/arch/powerpc/mm/fault.c
> +++ b/arch/powerpc/mm/fault.c
Acked-by: Jon Loeliger <jdl@freescale.com>
Tested on 8641HPCN.
Thanks,
jdl
next prev parent reply other threads:[~2007-07-19 16:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5d56173bee3f9ea0050aa508e7f27cc932af7229.1184104284.git.segher@kernel.crashing.org>
2007-07-12 9:47 ` [PATCH] Treat ISI faults as read faults on classic 32-bit PowerPC Johannes Berg
2007-07-18 15:30 ` Segher Boessenkool
2007-07-19 0:00 ` Paul Mackerras
2007-07-19 16:44 ` Jon Loeliger [this message]
2007-07-19 17:16 ` Segher Boessenkool
2007-07-19 18:57 ` Jon Loeliger
2007-07-19 19:02 ` Scott Wood
2007-07-19 19:10 ` Jon Loeliger
2007-07-19 20:59 ` Kumar Gala
2007-07-19 18:46 ` Segher Boessenkool
2007-07-19 23:40 ` Paul Mackerras
2007-07-20 7:42 ` Segher Boessenkool
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=1184863497.16820.8.camel@ld0161-tx32 \
--to=jdl@freescale.com \
--cc=johannes@sipsolutions.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).