xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Dong, Eddie" <eddie.dong@intel.com>,
	Christoph Egger <Christoph.Egger@amd.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 01/14] Nested Virtualization: tools
Date: Tue, 17 Aug 2010 08:35:29 +0100	[thread overview]
Message-ID: <C88FFA51.1E0D3%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <1A42CE6F5F474C41B63392A5F80372B2291436C6@shsmsx501.ccr.corp.intel.com>

On 17/08/2010 08:19, "Dong, Eddie" <eddie.dong@intel.com> wrote:

>>      xc_get_hvm_param(xch, domid, HVM_PARAM_PAE_ENABLED, &pae);
>>      is_pae = !!pae;
>> 
>> +    xc_get_hvm_param(xch, domid, HVM_PARAM_NESTEDHVM, &nestedhvm);
> 
> If you insist to support cross vendor nested virtualization, I would like to
> suggest we have multiple options for configuration: VMX, SVM, or HW.
> VMX and SVM option is for what situation that the user want to enforce the
> guest VMX/SVM features regardless of underlying hardware, while HW means to
> implements same with underlying virtualization feature in guest. In this way,
> it provides room for either cross vendor nested virtualization or natively
> virtualization.

We don't want cross-vendor nested virt, ever. So a simple boolean is fine
imo.

 -- Keir

  reply	other threads:[~2010-08-17  7:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-17  7:19 RE: [PATCH 01/14] Nested Virtualization: tools Dong, Eddie
2010-08-17  7:35 ` Keir Fraser [this message]
2010-08-17  7:54   ` Dong, Eddie
2010-08-17 10:07     ` Christoph Egger
2010-08-17 11:01 ` Christoph Egger
2010-08-17 14:18   ` Dong, Eddie
  -- strict thread matches above, loose matches on Subject: below --
2010-08-05 14:59 Christoph Egger
2010-08-05 16:21 ` 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=C88FFA51.1E0D3%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.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 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).