From: Paolo Bonzini <pbonzini@redhat.com>
To: Abel Gordon <abel@stratoscale.com>
Cc: Hu Yaohui <loki2441@gmail.com>, Bandan Das <bsd@redhat.com>,
kvm <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Muli Ben-Yehuda <muli@stratoscale.com>
Subject: Re: KVM Nested L2 guest startup problems
Date: Wed, 07 May 2014 13:40:01 +0200 [thread overview]
Message-ID: <536A1B91.2070103@redhat.com> (raw)
In-Reply-To: <536A1AEA.9020309@redhat.com>
Il 07/05/2014 13:37, Paolo Bonzini ha scritto:
> Il 07/05/2014 13:16, Abel Gordon ha scritto:
>>> > PLE should be left enabled, I think.
>> Well... the PLE settings L0 uses to run L1 (vmcs01) may be different
>> than the PLE settings L1 configured to run L2 (vmcs12).
>> For example, L0 can use a ple_gap to run L1 that is bigger than the
>> ple_gap L1 configured to run L2. Or L0 can use a ple_window to run L1
>> that is smaller than the ple_window L1 configured to run L2.
>
> That's correct. We should leave PLE enabled while running L2, but hide
> the feature altogether from L1.
... which we already do. The only secondary execution controls we allow
are APIC page, unrestricted guest, WBINVD exits, and of course EPT.
Paolo
next prev parent reply other threads:[~2014-05-07 11:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 1:43 KVM Nested L2 guest startup problems Hu Yaohui
2014-05-02 9:53 ` Paolo Bonzini
2014-05-02 15:17 ` Hu Yaohui
2014-05-02 15:52 ` Paolo Bonzini
2014-05-02 17:07 ` Hu Yaohui
2014-05-02 18:39 ` Bandan Das
2014-05-02 20:11 ` Hu Yaohui
2014-05-04 14:57 ` Abel Gordon
2014-05-04 16:33 ` Hu Yaohui
2014-05-07 8:58 ` Paolo Bonzini
2014-05-07 11:16 ` Abel Gordon
2014-05-07 11:37 ` Paolo Bonzini
2014-05-07 11:40 ` Paolo Bonzini [this message]
2014-05-07 15:30 ` Abel Gordon
2014-05-07 15:41 ` Paolo Bonzini
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=536A1B91.2070103@redhat.com \
--to=pbonzini@redhat.com \
--cc=abel@stratoscale.com \
--cc=bsd@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loki2441@gmail.com \
--cc=muli@stratoscale.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).