From: Paolo Bonzini <pbonzini@redhat.com>
To: Luwei Kang <luwei.kang@intel.com>, kvm@vger.kernel.org
Cc: rkrcmar@redhat.com, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, x86@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: Tue, 17 Oct 2017 14:13:12 +0200 [thread overview]
Message-ID: <66f40c86-cdf3-84a7-6d42-c0c7f6850e19@redhat.com> (raw)
In-Reply-To: <1508155781-4576-1-git-send-email-luwei.kang@intel.com>
On 16/10/2017 14:09, Luwei Kang wrote:
> 2. Enabling use of EPT to redirect PT output.
> — This enables the VMM to elect to virtualize the PT output buffer using EPT. In this mode, the CPU will treat PT output addresses as Guest Physical Addresses (GPAs) and translate them using EPT. This means that Intel PT output reads (of the ToPA table) and writes (of trace output) can cause EPT violations, and other output events.
Yay yay yay! ;)
> Intel Processor Trace virtualization can be work in one of 4 possible modes by set new option "pt_mode". Default is host guest mode.
> a. system-wide: trace both host/guest and output to host buffer;
> b. host-only: only trace host and output to host buffer;
> c. guest-only: only trace guest and output to guest buffer;
> d. host-guest: trace host/guest simultaneous and output to their respective buffer.
I think the guest-only mode isn't particularly useful, and I would
remove it.
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.
Paolo
next prev parent reply other threads:[~2017-10-17 12:13 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 [this message]
2017-10-18 10:18 ` Kang, Luwei
2017-10-18 10:30 ` Paolo Bonzini
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=66f40c86-cdf3-84a7-6d42-c0c7f6850e19@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
all inboxes | Powered by JetHome®