From: Paolo Bonzini <pbonzini@redhat.com>
To: "Kang, Luwei" <luwei.kang@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Cc: "rkrcmar@redhat.com" <rkrcmar@redhat.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Chao Peng <chao.p.peng@linux.intel.com>
Subject: Re: [PATCH 0/9] Intel Processor Trace virtulization enabling
Date: Wed, 18 Oct 2017 12:30:49 +0200 [thread overview]
Message-ID: <0ca0d53b-640a-c124-08dc-dbf009e01a8e@redhat.com> (raw)
In-Reply-To: <82D7661F83C1A047AF7DC287873BF1E167E1B5FB@SHSMSX101.ccr.corp.intel.com>
On 18/10/2017 12:18, Kang, Luwei wrote:
>> Nested virtualization is interesting. We would like the nested
>> hypervisor to be forced to set the "use GPA for processor tracing"
>> secondary execution control whenever "enable EPT" is set and
>> RTIT_CTL is nonzero. There is no way to encode that in
>> IA32_VMX_PROCBASED_CTLS2, however. It would be nice if Intel could
>> reserve a bit in IA32_VMX_EPT_VPID_CAP for KVM to express that
>> constraint.
>
> Do you mean if nested hypervisor get the capability of "Guest PT use
> GPA" and EPT has enable. Highly recommend nested hypervisor set "
> Guest PT use GPA " as well.
Well, it's required more than recommended. However, it's only required
if "enable EPT" is set and RTIT_CTL is nonzero.
> If nested hypervisor is also KVM, "use GPA for processor tracing"
> will be set for sure. But other hypervisor may not do that. So, we'd
> better add a flag in IA32_VMX_EPT_VPID_CAP to express that
> constraint.
Correct. The constraint would be:
* RTIT_CTL on entry is zero if EPT is disabled
* RTIT_CTL on entry is zero if EPT is enabled and "Guest PT uses GPA" is
zero
Maybe IA32_VMX_EPT_VPID_CAP is not the best place. I'll let Intel
decide that.
Paolo
next prev parent reply other threads:[~2017-10-18 10:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 12:09 Luwei Kang
2017-10-17 12:13 ` Paolo Bonzini
2017-10-18 10:18 ` Kang, Luwei
2017-10-18 10:30 ` Paolo Bonzini [this message]
2017-10-18 11:06 ` Kang, Luwei
2017-10-18 11:22 ` Paolo Bonzini
2017-10-19 5:54 ` Kang, Luwei
2017-10-19 7:14 ` Paolo Bonzini
2017-10-20 0:22 ` Kang, Luwei
2017-10-20 8:58 ` Paolo Bonzini
2017-10-23 8:01 ` Kang, Luwei
2017-10-23 14:40 ` Paolo Bonzini
2017-10-18 12:53 ` Stefan Hajnoczi
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=0ca0d53b-640a-c124-08dc-dbf009e01a8e@redhat.com \
--to=pbonzini@redhat.com \
--cc=chao.p.peng@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luwei.kang@intel.com \
--cc=mingo@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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
Powered by JetHome