All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: oritw@il.ibm.com
Cc: kvm@vger.kernel.org, benami@il.ibm.com, abelg@il.ibm.com,
	muli@il.ibm.com, aliguori@us.ibm.com, mdday@us.ibm.com
Subject: Re: Nested VMX support v3
Date: Tue, 20 Oct 2009 12:30:34 +0900	[thread overview]
Message-ID: <4ADD2EDA.7060700@redhat.com> (raw)
In-Reply-To: <1255617706-13564-1-git-send-email-oritw@il.ibm.com>

On 10/15/2009 11:41 PM, oritw@il.ibm.com wrote:
> Avi,
> We have addressed all of the comments, please apply.
>
> The following patches implement nested VMX support. The patches enable a guest
> to use the VMX APIs in order to run its own nested guest (i.e., enable running
> other hypervisors which use VMX under KVM). The current patches support running
> Linux under a nested KVM using shadow page table (with bypass_guest_pf
> disabled). SMP support was fixed.  Reworking EPT support to mesh cleanly with
> the current shadow paging design per Avi's comments is a work-in-progress.
>    

Why is bypass_guest_pf disabled?

> The current patches only support a single nested hypervisor, which can only run
> a single guest (multiple guests are work in progress). Only 64-bit nested
> hypervisors are supported.
>    

Multiple guests and 32-bit support are merge requirements.  As far as I 
can tell there shouldn't be anything special required to support them?


> vpid allocation will be updated with the multiguest support (work in progress).
> We are working on fixing the cr0.TS handling, it works for nested kvm by not
> for vmware server.
>    

Please either drop or fix vpid before merging.  What's wrong with 
cr0.ts?  I'd like to see that fixed as well.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.


  parent reply	other threads:[~2009-10-20  3:30 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-15 14:41 Nested VMX support v3 oritw
2009-10-15 14:41 ` [PATCH 1/5] Nested VMX patch 1 implements vmon and vmoff oritw
2009-10-15 14:41   ` [PATCH 2/5] Nested VMX patch 2 implements vmclear oritw
2009-10-15 14:41     ` [PATCH 3/5] Nested VMX patch 3 implements vmptrld and vmptrst oritw
2009-10-15 14:41       ` [PATCH 4/5] Nested VMX patch 4 implements vmread and vmwrite oritw
2009-10-15 14:41         ` [PATCH 5/5] Nested VMX patch 5 implements vmlaunch and vmresume oritw
2009-10-19 17:29           ` Gleb Natapov
2009-10-21 14:43             ` Orit Wasserman
2009-10-22  9:04               ` Gleb Natapov
2009-10-22 15:46                 ` Orit Wasserman
2009-10-25  9:44                   ` Gleb Natapov
2009-10-28 16:23                     ` Orit Wasserman
2009-10-29 17:31                       ` Gleb Natapov
2009-11-09  9:33                         ` Abel Gordon
2009-10-22 10:55               ` Avi Kivity
2009-10-20  4:56           ` Avi Kivity
2009-10-22 12:56             ` Orit Wasserman
2009-10-19 13:17         ` [PATCH 4/5] Nested VMX patch 4 implements vmread and vmwrite Gleb Natapov
2009-10-21 13:32           ` Orit Wasserman
2009-10-20  4:44         ` Avi Kivity
2009-10-22 12:50           ` Orit Wasserman
2009-10-19 11:17       ` [PATCH 3/5] Nested VMX patch 3 implements vmptrld and vmptrst Gleb Natapov
2009-10-21 13:27         ` Orit Wasserman
2009-10-19 12:59       ` Gleb Natapov
2009-10-21 13:28         ` Orit Wasserman
2009-10-20  4:24       ` Avi Kivity
2009-10-22 12:48         ` Orit Wasserman
2009-10-20  4:06     ` [PATCH 2/5] Nested VMX patch 2 implements vmclear Avi Kivity
2009-10-21 14:56       ` Orit Wasserman
2009-10-20  4:00   ` [PATCH 1/5] Nested VMX patch 1 implements vmon and vmoff Avi Kivity
2009-10-22 12:41     ` Orit Wasserman
2009-10-19 10:47 ` Nested VMX support v3 Gleb Natapov
2009-10-20  3:30 ` Avi Kivity [this message]
2009-10-21 14:50   ` Orit Wasserman

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=4ADD2EDA.7060700@redhat.com \
    --to=avi@redhat.com \
    --cc=abelg@il.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=benami@il.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=mdday@us.ibm.com \
    --cc=muli@il.ibm.com \
    --cc=oritw@il.ibm.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.