[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 16:09:35 -0700
  • Cc: Xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 28 Feb 2006 23:10:02 +0000
  • Domainkey-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=IUfGuV/d3FuNcuvDvS02LvFSdfN9BjzIMwqd/lLEykDI6wwCq0tNeKkesWPI/A6FS+t4s2HiZgA7FYbXSqwVuXvzMPgd0N4201ieiKgugeaCXggXsPyjxKUZ/DP17qXPteTZ+oQQ9NuCQeyNKgwPKriopZaKHhkv6eGrbzdadIA=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

My understanding is that
1) There will be only one hypercall at any point of time( there is no queue). Is this right?
2) This hypercall can poll for events/work to do in case it is preemptable. Is there any way that the hypercall can be made non-preemptable?
On 2/28/06, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:

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

> 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?

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

-- Keir

Xen-devel mailing list



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