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] [PATCH RFC V5 00/11] Paravirtualized ticketlocks

To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
Subject: RE: [Xen-devel] [PATCH RFC V5 00/11] Paravirtualized ticketlocks
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Thu, 13 Oct 2011 22:26:34 +1100
Cc: Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 13 Oct 2011 04:27:39 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4E968D24.8040509@xxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <cover.1318466916.git.jeremy.fitzhardinge@xxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01E5E5CA@trantor> <4E968D24.8040509@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcyJdmJUdmxuGd8BQoiAHlh10NLiEAAIPiZQ
Thread-topic: [Xen-devel] [PATCH RFC V5 00/11] Paravirtualized ticketlocks
> 
> On 10/12/2011 07:50 PM, James Harper wrote:
> >> Thoughts? Comments? Suggestions?
> >>
> > I am lead to believe that Hyper-V guests provide some sort of
spinlock
> > notification (a commit to KVM seems to suggest it). Has that been
> > considered at all here, if such notification can be exposed to Xen?
> >
> 
> Yes, that's basically what this series is about: a mechanism for Linux
to tell
> Xen "I'm stuck in a spinlock".
> 

Has it actually been implemented for Hyper-V though? It would appear
that a Hyper-V "HvNotifyLongSpinWait" hypercall is required to convey
spinlock information from the Windows DomU to Xen... AFAIK we don't
support any Hyper-V hypercalls right?

James


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

<Prev in Thread] Current Thread [Next in Thread>