Re: [Xen-devel] PATH: start_pfn field in xen_domctl_getmemlist_t

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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-devel] PATH: start_pfn field in xen_domctl_getmemlist_t, Tristan Gingold Re: [Xen-devel] PATH: start_pfn field in xen_domctl_getmemlist_t, Hollis Blanchard <= Re: [Xen-devel] PATH: start_pfn field in xen_domctl_getmemlist_t, Tristan Gingold

Previous by Date:

Re: [Xen-devel] xenconsoled CPU denial of service problem, Daniel P. Berrange

Next by Date:

[Xen-devel] [PATCH] wrong accounting in direct_remap_pfn_range, Steven Rostedt

Previous by Thread:

[Xen-devel] PATH: start_pfn field in xen_domctl_getmemlist_t, Tristan Gingold

Next by Thread:

Re: [Xen-devel] PATH: start_pfn field in xen_domctl_getmemlist_t, Tristan Gingold

Indexes:

[Date] [Thread] [Top] [All Lists]