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

[XenPPC] Re: [Xen-devel] [TOOLS][RFC] xc_get_pfn_list() and getmemlist.s

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: [XenPPC] Re: [Xen-devel] [TOOLS][RFC] xc_get_pfn_list() and getmemlist.start_pfn
From: Jimi Xenidis <jimix@xxxxxxxxxxxxxx>
Date: Fri, 20 Oct 2006 09:53:02 -0400
Cc: Gerd Hoffmann <kraxel@xxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, XenPPC-devel <xen-ppc-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 20 Oct 2006 12:02:10 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C15E8A90.2DC5%Keir.Fraser@xxxxxxxxxxxx>
List-help: <mailto:xen-ppc-devel-request@lists.xensource.com?subject=help>
List-id: Xen PPC development <xen-ppc-devel.lists.xensource.com>
List-post: <mailto:xen-ppc-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C15E8A90.2DC5%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-ppc-devel-bounces@xxxxxxxxxxxxxxxxxxx

On Oct 20, 2006, at 9:15 AM, Keir Fraser wrote:




On 20/10/06 13:29, "Gerd Hoffmann" <kraxel@xxxxxxx> wrote:

I'm not after the xc_get_pfn_list hypercall, but the (appearently?)
other hypercall Keir mentioned ...

Could be xc_domain_memory_increase_reservation() or
xc_domain_memory_populate_physmap() ...

Oh, it's called from xend python land somewhere... :-)

If you were not using python, or if the python was updated to actually obtain the list (passes a NULL pointer): ./python/xen/lowlevel/xc/xc.c:708:static PyObject *pyxc_domain_memory_increase_reservation()

one could easily build a pfn_to_mfn data structure on the tools side rather than get this huge array later.

This would be tremendously useful on PPC because the we typically do not use an order of 0 but large values (for large/super pages) that the data structure could be much more compact.
Baby steps will get us there.

BTW: not sure what xc_domain_memory_populate_physmap() does, looks like it can specify where in PFN space that allocated MFN are placed.

-JX


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