[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Design question for PV superpage support

  • To: Dave McCracken <dcm@xxxxxxxx>
  • From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
  • Date: Mon, 02 Mar 2009 17:15:43 -0800
  • Cc: Xen Developers List <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Mon, 02 Mar 2009 17:16:18 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Dave McCracken wrote:
The solution I am working on for how to support Linux hugepages (Xen superpages) involves creating domains made up entirely of superpages. I can create a working domain with superpages and am in the process of supporting it in save/restore.

For this to work properly this should be an attribute of a domain, specified somewhere in domain configuration and attached to that domain for its lifetime. This way it could be checked at memory populate time, save/restore time, and by the various balloon drivers.

My question is for those of you who best know the overall Xen design principles. Where should the flag be specified by the user? Where should it best be set in the running domain? I've seen some examples of flags being passed around, but would like some guidance on the best place to put it to fit into the Xen design.

One thing I'm not quite sure about: when you support 2M pages for a domain, is it fully-supported, to the extent you can safely set PSE in cpuid, and allow the guest kernel to use 2M mappings as it usually would? Or are there further restrictions?

You should support a feature flag in the guest kernel's ELF notes to say that it support large PV pages. If the kernel asks for it, then you can enable PSE in cpuid, or have some other mechanism for the kernel to query that the feature is available.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.