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

Re: [Xen-devel] Clock interrupts + hypervisor calls

To: "sowmya dayanand" <sowmyad@xxxxxxxxx>
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 28 Feb 2006 20:22:01 +0000
Cc: Xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 28 Feb 2006 20:24:11 +0000
List-id: Xen developer discussion <xen-devel.lists.xensource.com>


On 28 Feb 2006, at 19:22, sowmya dayanand wrote:

Is there a flag that the long-lived hypercalls set to indicate thatthey can be preempted? Also is the flag per-domain to indicate thatthe hypercall is in progress in the particular domain?

Preemption is voluntary. Long-lived hypercalls poll for pending events/ work to do.


 -- Keir


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

Follow-Ups:
- Re: [Xen-devel] Clock interrupts + hypervisor calls
  - From: sowmya dayanand

References:
- [Xen-devel] Clock interrupts + hypervisor calls
  - From: sowmya dayanand
- Re: [Xen-devel] Clock interrupts + hypervisor calls
  - From: Keir Fraser
- Re: [Xen-devel] Clock interrupts + hypervisor calls
  - From: sowmya dayanand

Prev by Date: [Xen-devel] [PATCH][SVM] svm 64bit initial support
Next by Date: Re: [Xen-devel] Common entry, exit point for hypervisor calls
Previous by thread: Re: [Xen-devel] Clock interrupts + hypervisor calls
Next by thread: Re: [Xen-devel] Clock interrupts + hypervisor calls
Index(es):
- Date
- Thread

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