| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
 Re: [Xen-devel] Clock interrupts + hypervisor calls
 
To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>From: "sowmya dayanand" <sowmyad@xxxxxxxxx>Date: Tue, 28 Feb 2006 12:22:05 -0700Cc: Xen-devel@xxxxxxxxxxxxxxxxxxxDelivery-date: Tue, 28 Feb 2006 19:22:33 +0000Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;	b=kzRh4LXekQz4LZDTrKoYsXUab3JQC0bS7uUEwboYVJJVXWEDXamEmC25rB0XdQgikC5ZUFxMCJyKdE+g/rxMWgf1WJzSAHMbmZr77R40I3BTWsPgHs41Y1XAnfh2ges8tnABIDywULwjtrRJ+9I07Z79igHbgIB9yOl6zE2DpD8=List-id: Xen developer discussion <xen-devel.lists.xensource.com> 
   Is there a flag that the long-lived hypercalls set to indicate that they can be preempted? Also is the flag per-domain to indicate that the hypercall is in progress in the particular domain?   Thanks, Sowmya.
 
 On 2/21/06, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:
On 21 Feb 2006, at 07:39, sowmya dayanand wrote:
 
 > Hi All,
 >
 > I wanted to know if a clock interrupt from any of the guest OS
 > interrupt/preempt a hypervisor call in xen?
 >
 > Eg: say the disk access hy per call is in progress and a guest OS on
 > another domain generates a clock interrupt, can this interrupt be
 > handled in the middle of the hypervisor call or does it have to wait?
 
 There is no disc access hypercall as Xen does not do I/O itself.
 Long-lived hypercalls can be voluntarily preempted by events. The
 hypercall is resumed without the guest needing to do anything special.
 
 -- Keir
 
 
 
 _______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
 
 |