From: Tim Deegan <Tim.Deegan@citrix.com>
To: "Dong, Eddie" <eddie.dong@intel.com>
Cc: Christoph Egger <Christoph.Egger@amd.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 07/14] Nested Virtualization: trap
Date: Tue, 31 Aug 2010 11:34:03 +0100 [thread overview]
Message-ID: <20100831103403.GC23648@whitby.uk.xensource.com> (raw)
In-Reply-To: <1A42CE6F5F474C41B63392A5F80372B22A648522@shsmsx501.ccr.corp.intel.com>
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@citrix.com>
Principal Software Engineer, XenServer Engineering
Citrix Systems UK Ltd. (Company #02937203, SL9 0BG)
next prev parent reply other threads:[~2010-08-31 10:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1A42CE6F5F474C41B63392A5F80372B22A3E5B97@shsmsx501.ccr.corp.intel.com>
2010-08-19 2:44 ` [PATCH 07/14] Nested Virtualization: trap Dong, Eddie
2010-08-19 8:35 ` Tim Deegan
2010-08-19 10:32 ` Christoph Egger
2010-08-19 14:12 ` Dong, Eddie
2010-08-19 13:53 ` Dong, Eddie
2010-08-19 14:30 ` Tim Deegan
2010-08-23 3:12 ` Dong, Eddie
2010-08-31 10:34 ` Tim Deegan [this message]
2010-08-23 16:03 ` Christoph Egger
2010-08-05 15:02 Christoph Egger
2010-08-09 12:44 ` Tim Deegan
2010-08-10 8:55 ` Christoph Egger
2010-08-10 10:48 ` Tim Deegan
2010-08-10 12:25 ` Christoph Egger
2010-08-10 12:56 ` Tim Deegan
2010-08-10 13:37 ` Christoph Egger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100831103403.GC23648@whitby.uk.xensource.com \
--to=tim.deegan@citrix.com \
--cc=Christoph.Egger@amd.com \
--cc=eddie.dong@intel.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.