WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH 1/1] Xen PV support for hugepages

To: Dave McCracken <dcm@xxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 1/1] Xen PV support for hugepages
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Fri, 07 Nov 2008 10:07:27 -0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Fri, 07 Nov 2008 10:07:51 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200811070839.25658.dcm@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20081104154149.21144.75675.sendpatchset@xxxxxxxxxxxxxxxxxxx> <200811060744.57275.dcm@xxxxxxxx> <49130785.76E4.0078.0@xxxxxxxxxx> <200811070839.25658.dcm@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.17 (X11/20081009)
Dave McCracken wrote:
On Thursday 06 November 2008, Jan Beulich wrote:
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.

Hmm... Sounds like a per-domain flag would be a good solution here. I'll look into it.

I think a guest should explicitly enable large page support via something like vmassist. In other words:

   * keep PSE clear - you are not implementing something similar to PSE
   * export the ability to map large pages via a feature flag or something
   * require guests to explicitly enable large page support


I'm sceptical about the value of this patch as it stands. We already have a vast number of operating modes and combinations, and I think we need to have a pretty high bar before adding any more. If this work arranged things so that we could just set PSE - and thereby make supporting it on the guest side much simpler - then I think the decision to include it would be easier.

In practical terms, I think this means that we need to modify Xen and the domain builder to *always* allocate memory to guests in 2M contig chunks, and then sort out all the tricky details ;) In practice, however, we would lose a lot of the benefit of doing this we'd get from the native kernel, because all the RO pagetable mappings would chop up the linear and kernel maps so much that we'd not get much chance to use the 2M mappings. It would, however, make hugetlbfs work without much drama.

   J

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel