From: Joerg Roedel <joro@8bytes.org>
To: Tim Deegan <Tim.Deegan@citrix.com>
Cc: Christoph Egger <Christoph.Egger@amd.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Qing He <qing.he@intel.com>
Subject: Re: Fwd: [PATCH 0/18] Nested Virtualization: Overview
Date: Sat, 17 Apr 2010 13:43:20 +0200 [thread overview]
Message-ID: <20100417114320.GC23260@8bytes.org> (raw)
In-Reply-To: <20100416102711.GA31304@whitby.uk.xensource.com>
On Fri, Apr 16, 2010 at 11:27:11AM +0100, Tim Deegan wrote:
> At 10:32 +0100 on 16 Apr (1271413945), Christoph Egger wrote:
> Your PDFs suggest that even on Intel CPUs, the nested hypervisor should
> always see SVM, not VMX. You shouldn't be surprised or offended if that
> isn't popular with Intel. :)
Well, it would make sense for Intel too virtualize SVM because it
doesn't has the performance issues with lots and lots of emulated
vmread/vmwrite instructions that cause vmexits in the nested case. The
bigger problem with SVM on VMX is that it could never be complete
because afaik VMX has fewer intercepts than SVM.
Joerg
next prev parent reply other threads:[~2010-04-17 11:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 13:20 Fwd: [PATCH 0/18] Nested Virtualization: Overview Christoph Egger
2010-04-15 13:39 ` Vincent Hanquez
2010-04-15 14:50 ` Christoph Egger
2010-04-15 14:51 ` Christoph Egger
2010-04-15 14:57 ` Keir Fraser
2010-04-15 15:17 ` Christoph Egger
2010-04-15 16:26 ` Keir Fraser
2010-04-15 15:25 ` Tim Deegan
2010-04-16 10:01 ` Christoph Egger
2010-04-16 9:07 ` Qing He
2010-04-16 9:32 ` Christoph Egger
2010-04-16 10:27 ` Tim Deegan
2010-04-16 17:50 ` Keir Fraser
2010-04-20 2:07 ` Dong, Eddie
2010-04-17 11:43 ` Joerg Roedel [this message]
2010-04-18 17:52 ` Keir Fraser
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=20100417114320.GC23260@8bytes.org \
--to=joro@8bytes.org \
--cc=Christoph.Egger@amd.com \
--cc=Tim.Deegan@citrix.com \
--cc=qing.he@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).