[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

To: Tristan Gingold <Tristan.Gingold@xxxxxxxx>
From: Hollis Blanchard <hollisb@xxxxxxxxxx>
Date: Tue, 29 Aug 2006 11:20:15 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 29 Aug 2006 09:20:05 -0700
List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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

Follow-Ups:
- Re: [Xen-devel] PATH: start_pfn field in xen_domctl_getmemlist_t
  - From: Tristan Gingold

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

Prev by Date: [Xen-devel] please pull xen-ia64-unstable.hg
Next by Date: Re: [Xen-ia64-devel] RFC: xencomm for xen/ia64
Previous by thread: [Xen-devel] PATH: start_pfn field in xen_domctl_getmemlist_t
Next by thread: Re: [Xen-devel] PATH: start_pfn field in xen_domctl_getmemlist_t
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.