From: Marcelo Tosatti <mtosatti@redhat.com>
To: "Nadav Har'El" <nyh@il.ibm.com>
Cc: Avi Kivity <avi@redhat.com>,
kvm@vger.kernel.org, "Tian, Kevin" <kevin.tian@intel.com>
Subject: Re: [PATCH] nVMX: Fix bug preventing more than two levels of nesting
Date: Thu, 2 Jun 2011 23:06:24 -0300 [thread overview]
Message-ID: <20110603020624.GC7272@amt.cnet> (raw)
In-Reply-To: <20110602085452.589883806F0@moren.haifa.ibm.com>
On Thu, Jun 02, 2011 at 11:54:52AM +0300, Nadav Har'El wrote:
> The nested VMX feature is supposed to fully emulate VMX for the guest. This
> (theoretically) not only allows it to run its own guests, but also also
> to further emulate VMX for its own guests, and allow arbitrarily deep nesting.
>
> This patch fixes a bug (discovered by Kevin Tian) in handling a VMLAUNCH
> by L2, which prevented deeper nesting.
>
> Deeper nesting now works (I only actually tested L3), but is currently
> *absurdly* slow, to the point of being unusable.
>
> Signed-off-by: Nadav Har'El <nyh@il.ibm.com>
Applied, thanks.
prev parent reply other threads:[~2011-06-03 2:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 8:54 [PATCH] nVMX: Fix bug preventing more than two levels of nesting Nadav Har'El
2011-06-03 2:06 ` Marcelo Tosatti [this message]
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=20110603020624.GC7272@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=nyh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox