WARNING - OLD ARCHIVES

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

xen-devel

Re: [Xen-devel] [PATCH 07/14] Nested Virtualization: trap

At 04:12 +0100 on 23 Aug (1282536722), Dong, Eddie wrote:
> > 
> > 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 :)

Well, since Christoph's done the work to pull out common logic I'd like
to see some of it used; but if it's going to be impossible, then we'll
start with whatever the two of you can agree on. :)

Tim.

-- 
Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Principal Software Engineer, XenServer Engineering
Citrix Systems UK Ltd.  (Company #02937203, SL9 0BG)

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