From: Richard Henderson <rth@twiddle.net>
To: Jamie Lokier <jamie@shareable.org>
Cc: linux-kernel@vger.kernel.org,
David Mosberger-Tang <davidm@hpl.hp.com>,
linux-ia64@linuxia64.org, Matthew Wilcox <matthew@wil.cx>,
Grant Grundler <grundler@parisc-linux.org>,
parisc-linux@parisc-linux.org,
Richard Curnow <Richard.Curnow@superh.com>,
Paul Mundt <lethal@linux-sh.org>,
linuxsh-shmedia-dev@lists.sourceforge.net,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Subject: Re: Comparing PROT_EXEC-only pages on different CPUs
Date: Thu, 1 Jul 2004 18:36:36 -0700 [thread overview]
Message-ID: <20040702013636.GA29154@twiddle.net> (raw)
In-Reply-To: <20040701224016.GB7928@mail.shareable.org>
On Thu, Jul 01, 2004 at 11:40:16PM +0100, Jamie Lokier wrote:
> Richard raises an interesting point: exec-only pages are useless if
> the code needs to read jump tables and constant pools. It seems very
> likely Alpha and IA64 have these.
Only if the processor is crippled enough that mixing jump tables and
constant pools in the same pages as code is considered reasonable.
Anyway, that's a strawman -- it's the toolchain's job to get the bits
on the pt_load segments correct.
If the pt_load segment or the mmap prot argument says execute-only,
then you should honor it.
r~
next prev parent reply other threads:[~2004-07-02 1:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 22:40 Comparing PROT_EXEC-only pages on different CPUs Jamie Lokier
2004-07-02 1:36 ` Richard Henderson [this message]
2004-07-02 4:02 ` Jamie Lokier
2004-07-02 14:51 ` Richard Curnow
2004-07-02 3:24 ` [parisc-linux] " John David Anglin
2004-07-02 4:07 ` Jamie Lokier
2004-07-03 0:39 ` John David Anglin
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=20040702013636.GA29154@twiddle.net \
--to=rth@twiddle.net \
--cc=Richard.Curnow@superh.com \
--cc=davidm@hpl.hp.com \
--cc=grundler@parisc-linux.org \
--cc=ink@jurassic.park.msu.ru \
--cc=jamie@shareable.org \
--cc=lethal@linux-sh.org \
--cc=linux-ia64@linuxia64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxsh-shmedia-dev@lists.sourceforge.net \
--cc=matthew@wil.cx \
--cc=parisc-linux@parisc-linux.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