From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Configuration of nestedhvm Date: Fri, 08 Oct 2010 08:12:04 +0100 Message-ID: References: <1A42CE6F5F474C41B63392A5F80372B22DBEA36C@shsmsx501.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1A42CE6F5F474C41B63392A5F80372B22DBEA36C@shsmsx501.ccr.corp.intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Dong, Eddie" Cc: Xen-devel List-Id: xen-devel@lists.xenproject.org On 08/10/2010 05:34, "Dong, Eddie" 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