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] [PATCH 07/14] Nested Virtualization: trap

To: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH 07/14] Nested Virtualization: trap
From: "Dong, Eddie" <eddie.dong@xxxxxxxxx>
Date: Mon, 23 Aug 2010 11:12:02 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: Christoph Egger <Christoph.Egger@xxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Dong, Eddie" <eddie.dong@xxxxxxxxx>
Delivery-date: Sun, 22 Aug 2010 20:19:42 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100819143056.GH20252@xxxxxxxxxxxxxxxxxxxxxxx>
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: <1A42CE6F5F474C41B63392A5F80372B22A3E5B97@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <1A42CE6F5F474C41B63392A5F80372B22A3E5C06@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20100819083552.GF20252@xxxxxxxxxxxxxxxxxxxxxxx> <1A42CE6F5F474C41B63392A5F80372B22A3E6083@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20100819143056.GH20252@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acs/qyx6DnZ/jlAKTdySp0wFwoRRkACxQNOA
Thread-topic: [Xen-devel] [PATCH 07/14] Nested Virtualization: trap
> If the new namespace of vmexit codes goes away entirely, that's fine
> by me, btw.  Maybe the generic code can pass exit codes as opaque

I suggest we don't generate a new namespace for l2 exit. If the vmexit/ementry 
handler of L2 guest can go to arch specific file, we are mostly in same page :)
For the rest of common functions, it is relatively easy to reach agreement IMO, 
including interrupt injection (I am kind of neutral though like arch-specific 
solution a little bit more).
I believe we will have some (medium) in EPT/NPT/Shadow side :)

> numbers, with a few flags to steer it?  Christoph, what do you think?
> You'll have the best idea of how useful the new namespace is.

Thanks, Eddie
Xen-devel mailing list