WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: "sowmya dayanand" <sowmyad@xxxxxxxxx>, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] Clock interrupts + hypervisor calls
From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
Date: Wed, 1 Mar 2006 11:40:25 +0100
Cc: Xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 01 Mar 2006 10:41:09 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcY8vJZ+5HskWzG5RzKAI6vRFFToPAAX3ptA
Thread-topic: [Xen-devel] Clock interrupts + hypervisor calls
 


From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of sowmya dayanand
Sent: 28 February 2006 23:10
To: Keir Fraser
Cc: Xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Clock interrupts + hypervisor calls

 
My understanding is that
1) There will be only one hypercall at any point of time( there is no queue). Is this right? 
No. In an SMP system there can be more than one Hypercall active at any given time - one per CPU.
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? 
 
Yes, you remove the poll-call. This will of course make the hypercall non-preemptable and it was probably made preemptable for a very good reason [lile somone found that it's working a lot better if you allow preemption at this point], so it's probably not such a great idea to do this.
 
--
Mats 
 
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
<Prev in Thread] Current Thread [Next in Thread>
  • RE: [Xen-devel] Clock interrupts + hypervisor calls, Petersson, Mats <=