From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>,
Dave McCracken <dave.mccracken@oracle.com>,
Jan Beulich <JBeulich@novell.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Re: Xen's use of PAT and PV guests
Date: Tue, 30 Mar 2010 11:25:32 -0700 [thread overview]
Message-ID: <4BB2421C.3060901@goop.org> (raw)
In-Reply-To: <C7D7FA76.F17A%keir.fraser@eu.citrix.com>
On 03/30/2010 10:59 AM, Keir Fraser wrote:
> As it happens I think we do only support CPUs that have PAT. But you can
> always check CPUID, just like running natively.
>
Yeah, I wasn't going to remove any of the tests, but I was wondering if
the guest can always assume that it can set the pat flags in the pte. I
guess that since Xen uses the same settings for the default pat (=no pat
at all), then so long as the guest doesn't try to set _PAGE_PAT, then it
doesn't matter.
Unfortunately hugetlbfs adds a wart, since it appears to end up going
down to the make_pte/pte_val path, but we can't tell whether its a page
with _PAGE_PSE or _PAGE_PAT set...
J
next prev parent reply other threads:[~2010-03-30 18:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 0:35 Xen's use of PAT and PV guests Jeremy Fitzhardinge
2010-03-30 7:44 ` Jan Beulich
2010-03-30 17:39 ` Jeremy Fitzhardinge
2010-03-30 17:59 ` Keir Fraser
2010-03-30 18:25 ` Jeremy Fitzhardinge [this message]
2010-03-30 16:57 ` Konrad Rzeszutek Wilk
2010-03-30 18:43 ` Jeremy Fitzhardinge
2010-03-31 8:26 ` Jan Beulich
2010-03-30 17:56 ` Ian Campbell
2010-03-30 21:47 ` Jeremy Fitzhardinge
2010-03-31 8:31 ` Ian Campbell
2010-03-31 16:55 ` Jeremy Fitzhardinge
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=4BB2421C.3060901@goop.org \
--to=jeremy@goop.org \
--cc=JBeulich@novell.com \
--cc=dave.mccracken@oracle.com \
--cc=keir.fraser@eu.citrix.com \
--cc=konrad.wilk@oracle.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.