From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Dave McCracken <dcm@mccr.org>
Cc: xen-devel@lists.xensource.com, Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: Re: [PATCH 2/2] Linux support for hugepages as a Xen PV guest
Date: Wed, 15 Oct 2008 14:48:22 -0700 [thread overview]
Message-ID: <48F66526.9050807@goop.org> (raw)
In-Reply-To: <200810151201.06367.dcm@mccr.org>
Dave McCracken wrote:
> For starters, Xen currently does remove PSE from the CPUID it returns to the
> guest. I'll add some code to allow PSE when hugepages are enabled.
>
Yep.
> Second, in Linux for the x86_64 architecture the macro to check for PSE is
> hard-wired to always be true.
>
Not in current kernels.
> Third, hugepages in Linux makes no check whatsoever for the presence or
> absence of PSE. It assumes it's there.
>
Not in current kernels. But it does assume that if PSE is present, then
physical memory can always be mapped with large pages.
> I'll look into the simplest way to make the various Linux parts obey the PSE
> flag properly.
>
No, use a current mainline git linux kernel.
J
next prev parent reply other threads:[~2008-10-15 21:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 13:29 [PATCH 1/2] Xen PV support for hugepages dcm
2008-10-10 13:30 ` [PATCH 2/2] Linux support for hugepages as a Xen PV guest dcm
2008-10-10 13:38 ` Keir Fraser
2008-10-10 15:06 ` Dave McCracken
2008-10-10 15:35 ` [PATCH 2/2] Linux support for hugepages as a Xen PVguest Jan Beulich
2008-10-15 17:01 ` Re: [PATCH 2/2] Linux support for hugepages as a Xen PV guest Dave McCracken
2008-10-15 21:48 ` Jeremy Fitzhardinge [this message]
2008-10-15 22:12 ` Dave McCracken
2008-10-15 22:31 ` Jeremy Fitzhardinge
2008-10-10 15:32 ` [PATCH 2/2] Linux support for hugepages as a Xen PVguest Jan Beulich
2008-10-10 15:28 ` [PATCH 1/2] Xen PV support for hugepages Jan Beulich
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=48F66526.9050807@goop.org \
--to=jeremy@goop.org \
--cc=dcm@mccr.org \
--cc=keir.fraser@eu.citrix.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.