From: "Jan Beulich" <jbeulich@novell.com>
To: Dave McCracken <dcm@mccr.org>
Cc: xen-devel@lists.xensource.com, Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [PATCH 1/1] Xen PV support for hugepages
Date: Thu, 06 Nov 2008 14:04:37 +0000 [thread overview]
Message-ID: <49130785.76E4.0078.0@novell.com> (raw)
In-Reply-To: <200811060744.57275.dcm@mccr.org>
>>> Dave McCracken <dcm@mccr.org> 06.11.08 14:44 >>>
>> Finally, no longer hiding X86_FEATURE_PSE from the guest seems rather
>> risky: I'm pretty sure the pv-ops kernel relies on this flag being clear -
>> when set, it would blindly (i.e. without ensuring the underlying memory is
>> contiguous and suitably aligned) try to use 2Mb mappings for e.g. the 1:1
>> mapping. I would think this capability ought to be propagated by another
>> means. Likewise I'm uncertain about letting X86_CR4_PSE shine through.
>>
>> And a general question: How is a trivial DomU going to be able to make
>> use of this, without being permitted to allocate non-order-zero chunks of
>> memory?
>
>This is the point of having hugepages a command line option. It should only
>be turned on if you intend to run guests who enforce the alignment rules.
You mean 'if you intend to run *only* guests ...', including dom0. Any guest
unaware of the connection of X86_FEATURE_PSE and the need to create
contiguous 2M chunks would fail, and any guest not having I/O memory
assigned would never manage to create such chunks.
Jan
next prev parent reply other threads:[~2008-11-06 14:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 15:41 [PATCH 1/1] Xen PV support for hugepages dcm
2008-11-05 10:59 ` Keir Fraser
2008-11-05 15:13 ` Jan Beulich
2008-11-06 13:44 ` Dave McCracken
2008-11-06 13:54 ` Keir Fraser
2008-11-06 14:04 ` Jan Beulich [this message]
2008-11-07 14:39 ` Dave McCracken
2008-11-07 18:07 ` 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=49130785.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--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.