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

To:	"Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject:	Re: [Xen-devel] Clock interrupts + hypervisor calls
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=
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to:	<e340752edf2e47379ecd223d8fdbaf42@xxxxxxxxxxxx>
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References:	<83c5685b0602202339k33eb2024qa8912e3b96aa9f10@xxxxxxxxxxxxxx> <a30df8ee80523d5ae3e0f2b3d94e3f9d@xxxxxxxxxxxx> <83c5685b0602281122m7fc60408rc8eed045af0ab6b2@xxxxxxxxxxxxxx> <e340752edf2e47379ecd223d8fdbaf42@xxxxxxxxxxxx>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

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?

Thanks,

Sowmya.

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

WARNING - OLD ARCHIVES

xen-devel

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