| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
RE: [Xen-devel] [PATCH RFC V5 00/11] Paravirtualized ticketlocks
Check the code in viridian.c. I think you'll find we do.
Paul
> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of James Harper
> Sent: 13 October 2011 12:27
> To: Jeremy Fitzhardinge
> Cc: Xen Devel
> Subject: RE: [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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home