[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] [PATCH RFC V5 00/11] Paravirtualized ticketlocks


  • To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
  • 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
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • 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


 


Rackspace

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