xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Christoph Egger <Christoph.Egger@amd.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: Tim Deegan <Tim.Deegan@eu.citrix.com>
Subject: Re: [PATCH 0/15] Nested Virtualization: Overview
Date: Thu, 3 Jun 2010 18:52:36 +0100	[thread overview]
Message-ID: <C82DAA74.16A30%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <C82DA1EF.16A14%keir.fraser@eu.citrix.com>

On 03/06/2010 18:16, "Keir Fraser" <keir.fraser@eu.citrix.com> wrote:

> Looks to me like this still unnecessarily tocuhes generic hvm code quite a
> lot. Take the CPUID patch for example. No reason for that to touch
> hvm_cpuid() when it properly belongs in the SVM-specific CPUID intercept
> routine. If you're stiull trying to peddle SVM-on-HVM -- remember noone else
> thought it was a good idea or wanted it. It won't fly.

Actually the CPUID patch was a bad one to pick out: it actually belongs in
xc_cpuid_x86.c, in the AMD-specific function therein, and it can work out
what to do based on reading the appropriate HVM_PARAM info from Xen. Which
is all nice and neat.

The other patch I actually read was #10, which modifies
hvm_interrupt_blocked(). Tbh, perhaps that one should stand: the alternative
is a SVM/VMX-specific function that calls out to the generic hvm function to
help it out (like what we do with CPUID). Maybe it's not worth it. It'd sure
be clearer if there were some nestedsvm_xxx() functions so we could read
things like:
  if ( nestedsvm_enabled(v->domain) && !nestedsvm_gif_isset(v) )
I mean, in this case, the whole concept of GIF is SVM-specific. Maybe it's
convenient to refer to it from a HVM-generic function in this context, but I
think the inherent SVM-ness of it should at least be clear.

Perhaps the rest isn't too bad really. Things like patch #4 *might* be
acceptable if Intel are going to use the hooks for their VMX-on-VMX work. If
not, I suspect some more culling of changes to generic code will be in
order.

 -- Keir
 
>  -- Keir
> 
> On 03/06/2010 17:02, "Christoph Egger" <Christoph.Egger@amd.com> wrote:
> 
>> 
>> Hi!
>> 
>> This patch series brings Nested Virtualization to Xen.
>> This is the second patch series with a lot of improvements
>> and fixes thanks to Tim Deegan's review.
>> 
>> The patch series:
>> 
>> patch 01: add nestedhvm guest config option to the tools.
>>                   This is the only one patch touching the tools
>> patch 02: change local_event_delivery_* to take vcpu argument.
>>                   This prevents spurios xen crashes on guest shutdown/destroy
>>                   with nestedhvm enabled.
>> patch 03: Add data structures for nested virtualization.
>> patch 04: add nestedhvm function hooks, described in XenNestedHVM.pdf
>> patch 05: The heart of nested virtualization.
>> patch 06: Allow switch to paged real mode during vmrun emulation.
>>                   Emulate cr0 and cr4 when guest does not intercept them
>>                   (i.e. Hyper-V/Windows7)
>> patch 07: Allow guest to enable SVM in EFER
>> patch 08: Propagate SVM cpuid feature bits to guest
>> patch 09: Emulate MSRs needed for nested virtualization
>> patch 10: Handle interrupts (generic part)
>> patch 11: SVM specific implementation for nested virtualization
>> patch 12: Handle interrupts (SVM specific)
>> patch 13: The piece of code that effectively turns nested virtualization on.
>>                   Use HVM_PARAM_* this time.
>> patch 14: Change p2m infrastructure to operate with per-p2m instead
>>                   of per-domain. Combined with patch 15, this allows to run
>>                   nested guest with hap-on-hap.
>> patch 15: Handle nested pagefault to enable hap-on-hap and handle
>>                   nested guest page-table-walks to emulate instructions
>>                   the guest does not intercept (i.e. WBINVD with Windows 7).
>> 
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  reply	other threads:[~2010-06-03 17:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-03 16:02 [PATCH 0/15] Nested Virtualization: Overview Christoph Egger
2010-06-03 17:16 ` Keir Fraser
2010-06-03 17:52   ` Keir Fraser [this message]
2010-06-04  9:44     ` Christoph Egger
2010-06-04 10:00       ` 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=C82DAA74.16A30%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=Christoph.Egger@amd.com \
    --cc=Tim.Deegan@eu.citrix.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).