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

["Dong, Eddie" <eddie.dong@xxxxxxxxx>]

> 
> 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
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel