Re: Re: [Xen-users] Xen viridian support/features

[Florian Manschwetus <florianmanschwetus@gmx.de>]

[-- Attachment #1.1: Type: text/plain, Size: 1264 bytes --]

Am 23.07.2009 16:19, schrieb Pasi Kärkkäinen:
> On Thu, Jul 23, 2009 at 03:11:01PM +0100, Tim Deegan wrote:
>> At 18:15 +0100 on 21 Jul (1248200133), Pasi K?rkk?inen wrote:
>>> Then again I'm not sure "how much" of viridian stuff Xen currently
>>> supports..
>> At the moment we provide MSR access to APIC registers, and the hypercall
>> to yield the CPU when waiting for a spinlock.  We looked at a few others
>> (e.g. address-space-change hypercall) but found the benefits, if any,
>> were negligible.
>>
>> The most important part of the interface is that we can use it to tell
>> Windows not to expect timer interrupt delivery to be as even across all
>> CPUs as it would be on bare metal.  This gets rid of annoying STOP 0x101
>> bluescreens in multi-vcpu Windows from Vista on.
>>
>
> Thanks for the reply!
>
> Any plans to write support for paravirtual viridian disk/network backends?
> (I assume they have stuff like that implemented in hyper-v).
>
> -- Pasi
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
Take a shorter target, reboot notification using hyper-v guest 
integration stuff would be a great win.

Florian


[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3686 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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