From: "Bruce Rogers" <BROGERS@novell.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>,
xen-devel@lists.xensource.com, Jan Beulich <JBeulich@novell.com>
Subject: Re: PAE issue (32-on-64 work)
Date: Thu, 19 Oct 2006 07:18:13 -0600 [thread overview]
Message-ID: <453726AF.092E.0048.1@novell.com> (raw)
In-Reply-To: <C15D34A3.2CB1%Keir.Fraser@cl.cam.ac.uk>
NetWare is also a PAE guest, but doesn't put anything in the rest of the page, so
zapping would be fine for NetWare.
- Bruce
>>> On 10/19/2006 at 6:56 AM, in message <C15D34A3.2CB1%Keir.Fraser@cl.cam.ac.uk>,
Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:
> On 19/10/06 11:39, "Jan Beulich" <jbeulich@novell.com> wrote:
>
>> Just now I found that there is a resulting issue for the 32on64 work I'm
>> doing: Since none of the entries 4...511 of the PMD get initialized in
> Linux,
>> and since Xen nevertheless has to validate all 512 entries (in order to
>> avoid making available translations that could be used during speculative
>> execution), the validation has the potential to fail (and does in reality),
>> resulting in the guest dying. The only option I presently see is to special
>> case the compatibility guest in the l3 handling and (I really hate to do
>> that) clear out the 518 supposedly unused entries (or at least clear
>> their present bits), meaning that no guest may ever make clever
>> assumptions and try to store some other data in the unused portion of
>> the pgd page.
>
> Either copy the PGDs out into a shadow L3, as we do for PAE Xen today. Or,
> as you say, zap the 508 unused entries. No guest uses them -- I'm pretty
> sure Linux is the only PAE-capable guest (others are non-pae or 64-bit).
> Storing other stuff in the page would be inconvenient anyway since it has to
> be read-only.
>
> -- Keir
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2006-10-19 13:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 10:39 PAE issue (32-on-64 work) Jan Beulich
2006-10-19 11:03 ` Ian Pratt
2006-10-19 11:18 ` Jan Beulich
2006-10-19 11:34 ` Ian Pratt
2006-10-19 12:58 ` Keir Fraser
2006-10-19 14:24 ` Jan Beulich
2006-10-19 14:26 ` Keir Fraser
2006-10-19 12:56 ` Keir Fraser
2006-10-19 13:18 ` Bruce Rogers [this message]
[not found] <E1GaYNL-0000rc-Ub@host-192-168-0-1-bcn-london>
2006-10-19 16:19 ` Joe Bonasera
2006-10-19 16:24 ` Keir Fraser
2006-10-19 17:22 ` Joe Bonasera
2006-10-19 18:48 ` Keir Fraser
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=453726AF.092E.0048.1@novell.com \
--to=brogers@novell.com \
--cc=JBeulich@novell.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--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.