linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gabriel Paubert <paubert@iram.es>
To: Paul Mackerras <paulus@samba.org>
Cc: 'Albert Cahalan' <acahalan@gmail.com>,
	debian-powerpc@lists.debian.org, linuxppc-dev@ozlabs.org
Subject: Re: PowerPC paxtest results w/ gcc-4.1
Date: Wed, 16 Aug 2006 12:59:25 +0200	[thread overview]
Message-ID: <20060816105925.GB21865@iram.es> (raw)
In-Reply-To: <17633.18057.778991.483461@cargo.ozlabs.ibm.com>

On Tue, Aug 15, 2006 at 01:59:05PM +1000, Paul Mackerras wrote:
> Matt Sealey writes:
> 
> > Book I compatible PowerPC's have had a "no-executable" bit in
> > the page protection flags since the dark ages.. see page 7-38
> > and 7-39 of the 'Programming Environments Manual for 32-Bit
> > Microprocessors'.. this document predates even the G3.
> 
> What are you referring to?  I have a copy of the PEM from pre-G3 days,
> and a copy that I downloaded just now, and neither of them have an N
> bit in the PTE (and yes I just looked carefully through pages 7-38 and
> 7-39).
> 
> There is an N bit in the segment register format, and that's what
> Albert is using.
> 
> > As far as the documentation goes, you can make the page
> > readable and writable to the LSU, but the N bit causes the
> > instruction fetch to cause a machine check. That's pretty
> > "not-executable" to me at least :)
> 
> A machine check is nasty, because it may not be recoverable...

I agree, but I don't know why you believe it would cause 
a machine check (0x200): from my docs, it is an ISI (0x400). 

BTW, there is one way to make pages non executable: mark
them as guarded, but it will have a significant cost in
terms of performance. 

I never understood why PTE entries waste 4 bits (WIMG)
for effectively very few valid combinations.

	Regards,
	Gabriel

  reply	other threads:[~2006-08-16 10:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-12  5:50 PowerPC paxtest results w/ gcc-4.1 Albert Cahalan
2006-08-12 11:35 ` Paul Mackerras
2006-08-12 14:36   ` Albert Cahalan
2006-08-12 23:54     ` Paul Mackerras
2006-08-13  2:48       ` Albert Cahalan
2006-08-13  3:23         ` Paul Mackerras
2006-08-13  4:11           ` Albert Cahalan
2006-08-13 16:45             ` Hollis Blanchard
2006-08-13 18:59               ` Albert Cahalan
2006-08-14 12:17             ` Matt Sealey
2006-08-14 14:20               ` Kumar Gala
2006-08-13  3:29       ` Alan Modra
2006-08-13 18:56       ` Albert Cahalan
2006-08-14 11:50       ` Matt Sealey
2006-08-15  3:59         ` Paul Mackerras
2006-08-16 10:59           ` Gabriel Paubert [this message]
2006-08-16 11:07             ` Paul Mackerras
2006-08-16 14:43               ` Albert Cahalan
2006-08-16 17:49             ` 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=20060816105925.GB21865@iram.es \
    --to=paubert@iram.es \
    --cc=acahalan@gmail.com \
    --cc=debian-powerpc@lists.debian.org \
    --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).