From: Russell King <rmk@arm.linux.org.uk>
To: Timur Tabi <ttabi@interactivesi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pte_val(*pte) as lvalue
Date: Tue, 3 Jul 2001 20:11:06 +0100 [thread overview]
Message-ID: <20010703201106.B31954@flint.arm.linux.org.uk> (raw)
In-Reply-To: <9LUWoC.A.W3G.sIQQ7@dinero.interactivesi.com.suse.lists.linux.kernel> <oupelryykh5.fsf@pigdrop.muc.suse.de> <LScPx.A.XAF.H_gQ7@dinero.interactivesi.com> <20010703194300.A31954@flint.arm.linux.org.uk> <3B4213DD.50005@interactivesi.com>
In-Reply-To: <3B4213DD.50005@interactivesi.com>; from ttabi@interactivesi.com on Tue, Jul 03, 2001 at 01:50:05PM -0500
On Tue, Jul 03, 2001 at 01:50:05PM -0500, Timur Tabi wrote:
> Russell King wrote:
> >Can I ask what the nature of the PTE modification is, and where you
> >are making this modification?
> >
> I've written a hack which enables PAT (Page Address Translation) for a
> particular page:
Firstly, I'll say I'm no x86 expert by any means. However, it may be
better to extend the pte bit handling functions in
include/asm-i386/pgtable.h to include the bits you need to handle.
(eg, see how pte_mkwrite and pte_wrprotect are implemented.) This is
probably the cleanest way of handling these bits.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2001-07-03 19:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9LUWoC.A.W3G.sIQQ7@dinero.interactivesi.com.suse.lists.linux.kernel>
2001-07-02 23:33 ` pte_val(*pte) as lvalue Andi Kleen
2001-07-03 19:55 ` eCos Matthew M. DeLoera
2001-07-03 18:32 ` pte_val(*pte) as lvalue Timur Tabi
2001-07-03 18:43 ` Russell King
2001-07-03 18:50 ` Timur Tabi
2001-07-03 19:11 ` Russell King [this message]
2001-07-02 23:22 Timur Tabi
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=20010703201106.B31954@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=ttabi@interactivesi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.