From: Keir Fraser <keir@xen.org>
To: "Dong, Eddie" <eddie.dong@intel.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Configuration of nestedhvm
Date: Fri, 08 Oct 2010 08:12:04 +0100 [thread overview]
Message-ID: <C8D482D4.256E2%keir@xen.org> (raw)
In-Reply-To: <1A42CE6F5F474C41B63392A5F80372B22DBEA36C@shsmsx501.ccr.corp.intel.com>
On 08/10/2010 05:34, "Dong, Eddie" <eddie.dong@intel.com> wrote:
> Nested virtualization usage model is emerging, however we must guarantee it
> won't impact the performance of simple virtualization.
> This patch add an boot parameter for nested virtualization, which is disabled
> by default for now.
What's the point when a per-domain config option is going to be implemented?
You can then simply not configure nestedhvm for a domain you want to test
without that capability? I suppose it makes your second patch make a bit
more sense than it would in total isolation.
I think patch#2 probably makes sense, but it should wait for the patch that
actually implements the per-domain config option, and properly implements
is_nestedhvm(), before going in.
-- Keir
next prev parent reply other threads:[~2010-10-08 7:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 0:28 build break in xl.c in python Kay, Allen M
2010-10-08 4:34 ` Configuration of nestedhvm Dong, Eddie
2010-10-08 7:12 ` Keir Fraser [this message]
2010-10-08 7:56 ` Dong, Eddie
2010-10-08 8:15 ` Keir Fraser
2010-10-08 8:22 ` Keir Fraser
2010-10-08 8:47 ` Dong, Eddie
2010-10-08 11:29 ` Keir Fraser
2010-10-08 8:44 ` Christoph Egger
2010-10-08 8:54 ` Dong, Eddie
2010-10-08 10:02 ` Christoph Egger
2010-10-08 13:33 ` Dong, Eddie
2010-10-08 13:48 ` Christoph Egger
2010-10-09 2:54 ` add missing VMCS definition Dong, Eddie
2010-10-08 8:28 ` build break in xl.c in python Gianni Tedesco
2010-10-08 8:33 ` Gianni Tedesco
2010-10-08 10:43 ` Stefano Stabellini
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=C8D482D4.256E2%keir@xen.org \
--to=keir@xen.org \
--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.