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


[Xen-devel] Re: [Qemu-devel] [PATCH 00/10] xen: pv domain support.

To: Alexander Graf <agraf@xxxxxxx>
Subject: [Xen-devel] Re: [Qemu-devel] [PATCH 00/10] xen: pv domain support.
From: Gerd Hoffmann <kraxel@xxxxxxxxxx>
Date: Mon, 06 Apr 2009 08:53:01 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Laurent Vivier <Laurent@xxxxxxxxx>, qemu-devel <qemu-devel@xxxxxxxxxx>
Delivery-date: Sun, 05 Apr 2009 23:53:43 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <88ADCEFD-E057-4264-8447-9E53A661B35D@xxxxxxx>
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: <1238621982-18333-1-git-send-email-kraxel@xxxxxxxxxx> <1238706878.5426.1.camel@Quad> <49D6708D.4000601@xxxxxxxxxx> <88ADCEFD-E057-4264-8447-9E53A661B35D@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20090320)
Alexander Graf wrote:
> One idea I had for full virtualization in a Xen environment would be an
> PV vmenter/vmexit framework - either by implementing a completely new
> abstraction or simple traps for privileged operations like VMRUN.
> That way we could have a kvm that talks to xen for the VM, rendering kvm
> useful on Xen dom0s, giving people the best of both worlds.

Hmm.  I suspect xen's direct paging mode makes that quite intrusive as
the kvm mmu code would have to know about this extra p2m translation
step to get the shadow/ept/ntp tables right.  Given that this most
likely would be a odd and rarely tested use case I don't think this
would be a good idea ...


Xen-devel mailing list

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