linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Gabriel Paubert <paubert@iram.es>
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 21:07:44 +1000	[thread overview]
Message-ID: <17634.64640.709200.871907@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20060816105925.GB21865@iram.es>

Gabriel Paubert writes:

> 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). 

I don't believe it would cause a machine check either, but that is
what Matt Sealey was saying.  I don't know where he got that idea.

> 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. 

Indeed.  I guess we could do that as a config option for machines that
really want maximum security at the expense of performance, but I
don't think all users would want that.

Paul.

  reply	other threads:[~2006-08-16 11:07 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
2006-08-16 11:07             ` Paul Mackerras [this message]
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=17634.64640.709200.871907@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=acahalan@gmail.com \
    --cc=debian-powerpc@lists.debian.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paubert@iram.es \
    /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).