From: "Scott Parish" <srparish@us.ibm.com>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: xen-devel@lists.xensource.com, Scott Parish <srparish@us.ibm.com>
Subject: Re: [patch] predicate NX flag
Date: Tue, 7 Jun 2005 20:47:16 +0000 [thread overview]
Message-ID: <20050607204716.GC14747@us.ibm.com> (raw)
In-Reply-To: <7F740D512C7C1046AB53446D37200173042FEC74@scsmsx402.amr.corp.intel.com>
On Tue, Jun 07, 2005 at 01:45:45PM -0700, Nakajima, Jun wrote:
> Scott Parish wrote:
> > the NX flag should only be set when its use is enabled.
> >
> > sRp
>
> Rather than changing __PAGE_KERNEL, I think we should change set_p?d (?
> = g, u, m, e) like
>
> #define set_pmd(pmdptr, pmdval) xen_l2_entry_update(pmdptr, (pmdval)&
> __supported_pte_mask)
Working on a patch.. there are places that xen_l1_entry_update() is
called directly with __PAGE_KERNEL, should those be converted to a
set_pte, or should xen_l1_entry_update be updated instead of the macros,
or should '& __supported_pte_mask' be hardcoded into these places. I'd
prefer to just modify the xen_l?_entry_update()s
btw, __supported_PTE_mask seems an unfortunate name for a mask that gets
used for other pagetable levels.
sRp
--
Scott Parish
Signed-off-by: srparish@us.ibm.com
next prev parent reply other threads:[~2005-06-07 20:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 20:45 [patch] predicate NX flag Nakajima, Jun
2005-06-07 20:47 ` Scott Parish [this message]
2005-06-07 20:49 ` Scott Parish
-- strict thread matches above, loose matches on Subject: below --
2005-06-07 21:52 Nakajima, Jun
2005-06-07 21:45 Ian Pratt
2005-06-07 21:02 Nakajima, Jun
2005-06-07 18:33 [patch] (resend) mask out nx bits when calculatingpfn/mfn Nakajima, Jun
2005-06-07 19:12 ` [patch] predicate NX flag Scott Parish
2005-06-08 19:24 ` David F Barrera
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=20050607204716.GC14747@us.ibm.com \
--to=srparish@us.ibm.com \
--cc=jun.nakajima@intel.com \
--cc=xen-devel@lists.xensource.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.