Xen devel - Aug 2006 - PATH: start_pfn field in xen_domctl_getmemlist_t

Hi,

Because getmemlist needs to be restartable and read P2M, xen/ia64 has always 
passed start_pfn info trough the hypercall.

Until now it was combined with max_pfns into the max_pfns field.  This was not 
very clean.  Because the API has just been changed I think this is the right 
time to make this small change.

Tested on xen/ia64.

Tristan.


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

On Tue, 2006-08-29 at 12:00 +0200, Tristan Gingold
wrote:
> 
> Because getmemlist needs to be restartable and read P2M, xen/ia64 has
always
> passed start_pfn info trough the hypercall.
By "restartable" you mean create a continuation? Why does getmemlist
need to be restartable only on IA64? Also, where does the IA64 code
create a continuation for it now?

-- 
Hollis Blanchard
IBM Linux Technology Center


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

Le Mardi 29 Août 2006 18:20, Hollis Blanchard a écrit :
> On Tue, 2006-08-29 at 12:00 +0200, Tristan Gingold wrote:
> > Because getmemlist needs to be restartable and read P2M, xen/ia64 has
> > always passed start_pfn info trough the hypercall.
>
> By "restartable" you mean create a continuation?
No.
getmemlist may fail during copy to guest, because of missing TLB entries.  We 
manually restart the call.
> Why does getmemlist
> need to be restartable only on IA64? Also, where does the IA64 code
> create a continuation for it now?
See xc_ia64_get_pfn_list in tools/libxc/ia64/xc_ia64_stubs.c

Tristan.


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