From: Andi Kleen <andi@firstfloor.org>
To: Jan Beulich <jbeulich@novell.com>
Cc: linux-kernel@vger.kernel.org, discuss@x86-64.org
Subject: Re: [discuss] pte_{ex,rd}protect
Date: Thu, 10 May 2007 13:30:45 +0200 [thread overview]
Message-ID: <20070510113045.GD14898@one.firstfloor.org> (raw)
In-Reply-To: <46430780.76E4.0078.0@novell.com>
On Thu, May 10, 2007 at 11:52:32AM +0200, Jan Beulich wrote:
> Various architectures define these, but they aren't being used anywhere -
> candidates for removal? The more that (at least) on i386 and x86-64
> pte_exprotect() is not symmetrical to pte_exec() and pte_mkexec()...
They should be removed everywhere imho
-Andi
next prev parent reply other threads:[~2007-05-10 11:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 9:52 pte_{ex,rd}protect Jan Beulich
2007-05-10 11:30 ` Andi Kleen [this message]
2007-05-10 15:53 ` pte_{ex,rd}protect Christoph Hellwig
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=20070510113045.GD14898@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=discuss@x86-64.org \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.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