From: Paul Mackerras <paulus@samba.org>
To: Wouter Cloetens <wouter@mind.be>
Cc: Trevor Woerner <ppc339@vtnet.ca>, linuxppc-dev@lists.linuxppc.org
Subject: Re: [PATCH 2.4.22] Re: PPC405 support in later 2.4.x kernels
Date: Sun, 31 Aug 2003 21:59:58 +1000 (EST) [thread overview]
Message-ID: <16209.58174.726345.22844@nanango.paulus.ozlabs.org> (raw)
In-Reply-To: <20030829150115.GD1204@roadkill.intern.mind.be>
Wouter Cloetens writes:
> On Thu, 31 Jul 2003 23:32:41 -0400, Trevor Woerner wrote:
> > I grabbed 2.4.22-pre8 and found the ppc4xx code back, but the strangest
> > thing is now happening: I've lost my user-space.
>
> I had the same problem with 2.4.22. I diffed 2.4.21-pre7 with 2.4.22
> and found some 405-specific code to be missing in the fault handler.
> The attached patch fixes the problem.
The patch is half of an optimization. We have ended up with code
which never sets execute permission on the PTEs (my fault). We should
either just add code (in the TLB miss handler or elsewhere) to set
execute permission on all pages, or else do the full lazy-flush
optimization, which involves the change in do_page_fault plus another
change to flush_icache_page to make it turn off hardware execute
permission rather than flushing the page. (The latter half doesn't
seem to be in linuxppc-2.4 or linuxppc_2_4_devel, which is
interesting.)
I'll check in a proper fix in the next day or so. In the meantime the
patch to do_page_fault will fix the problem.
Paul.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-08-31 11:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-29 15:01 [PATCH 2.4.22] Re: PPC405 support in later 2.4.x kernels Wouter Cloetens
2003-08-31 11:59 ` Paul Mackerras [this message]
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=16209.58174.726345.22844@nanango.paulus.ozlabs.org \
--to=paulus@samba.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=ppc339@vtnet.ca \
--cc=wouter@mind.be \
/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).