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/
Home Products Support Community News


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

To: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-devel] Re: [Xen-users] Xen viridian support/features
From: Florian Manschwetus <florianmanschwetus@xxxxxx>
Date: Thu, 23 Jul 2009 16:45:53 +0200
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Nathan Eisenberg <nathan@xxxxxxxxxxxxxxxx>, Tim Deegan <Tim.Deegan@xxxxxxxxxx>, "Xen-users@xxxxxxxxxxxxxxxxxxx" <Xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 23 Jul 2009 07:45:50 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20090723141953.GE24960@xxxxxxxxxxxxxxx>
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: <11B064048F34FD4094CBA16FC04BE2196072A843@ex01> <20090721072326.GN24960@xxxxxxxxxxxxxxx> <20090721171533.GT24960@xxxxxxxxxxxxxxx> <20090723141101.GF5235@xxxxxxxxxxxxxxxxxxxxx> <20090723141953.GE24960@xxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.1b3pre) Gecko/20090623 Thunderbird/3.0b2
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
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

Take a shorter target, reboot notification using hyper-v guest integration stuff would be a great win.


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Xen-devel mailing list