From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave McCracken Subject: Design question for PV superpage support Date: Mon, 2 Mar 2009 07:54:23 -0600 Message-ID: <200903020754.23534.dcm@mccr.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Xen Developers List List-Id: xen-devel@lists.xenproject.org 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. Thanks, Dave McCracken Oracle Corp.