From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, xiaoyao.li@intel.com
Subject: [PATCH v3 0/8] Make Intel PT configurable
Date: Thu, 8 Dec 2022 14:25:05 +0800 [thread overview]
Message-ID: <20221208062513.2589476-1-xiaoyao.li@intel.com> (raw)
Initial virtualization of Intel PT was added by making it as fixed
feature set of ICX's capabilities. However, it breaks the Intel PT exposure
on SPR machine because SPR has less PT capabilities of
CPUID(0x14,1):EBX[15:0].
This series aims to make Intel PT configurable that named CPU model can
define its own PT feature set and "-cpu host/max" can use host pass-through
feature set of Intel PT.
At the same time, it also ensures existing named CPU model to generate
the same PT CPUID set as before to not break live migration.
Changes in v3:
- rebase to v7.2.0-rc4
- Add bit 7 and 8 of FEAT_14_0_EBX in Patch 3
v2: https://lore.kernel.org/qemu-devel/20220808085834.3227541-1-xiaoyao.li@intel.com/
Changes in v2:
- split out 3 patches (per Eduardo's comment)
- determine if the named cpu model uses default Intel PT capabilities (to
be compatible with the old behavior) by condition that all PT feature
leaves are all zero.
v1: https://lore.kernel.org/qemu-devel/20210909144150.1728418-1-xiaoyao.li@intel.com/
Xiaoyao Li (8):
target/i386: Print CPUID subleaf info for unsupported feature
target/i386/intel-pt: Fix INTEL_PT_ADDR_RANGES_NUM_MASK
target/i386/intel-pt: Introduce FeatureWordInfo for Intel PT CPUID
leaf 0x14
target/i386/intel-pt: print special message for
INTEL_PT_ADDR_RANGES_NUM
target/i386/intel-pt: Rework/rename the default INTEL-PT feature set
target/i386/intel-pt: Enable host pass through of Intel PT
target/i386/intel-pt: Define specific PT feature set for
IceLake-server and Snowridge
target/i386/intel-pt: Access MSR_IA32_RTIT_ADDRn based on guest CPUID
configuration
target/i386/cpu.c | 293 +++++++++++++++++++++++++++++++-----------
target/i386/cpu.h | 40 +++++-
target/i386/kvm/kvm.c | 8 +-
3 files changed, 263 insertions(+), 78 deletions(-)
--
2.27.0
next reply other threads:[~2022-12-08 6:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 6:25 Xiaoyao Li [this message]
2022-12-08 6:25 ` [PATCH v3 1/8] target/i386: Print CPUID subleaf info for unsupported feature Xiaoyao Li
2022-12-08 6:25 ` [PATCH v3 2/8] target/i386/intel-pt: Fix INTEL_PT_ADDR_RANGES_NUM_MASK Xiaoyao Li
2022-12-08 6:25 ` [PATCH v3 3/8] target/i386/intel-pt: Introduce FeatureWordInfo for Intel PT CPUID leaf 0x14 Xiaoyao Li
2022-12-08 6:25 ` [PATCH v3 4/8] target/i386/intel-pt: print special message for INTEL_PT_ADDR_RANGES_NUM Xiaoyao Li
2022-12-09 6:43 ` Chenyi Qiang
2022-12-13 12:09 ` Xiaoyao Li
2022-12-14 1:48 ` Chenyi Qiang
2022-12-08 6:25 ` [PATCH v3 5/8] target/i386/intel-pt: Rework/rename the default INTEL-PT feature set Xiaoyao Li
2022-12-08 6:25 ` [PATCH v3 6/8] target/i386/intel-pt: Enable host pass through of Intel PT Xiaoyao Li
2022-12-09 6:55 ` Chenyi Qiang
2022-12-13 12:15 ` Xiaoyao Li
2023-02-21 5:14 ` Wang, Lei
2023-02-21 9:37 ` Xiaoyao Li
2022-12-08 6:25 ` [PATCH v3 7/8] target/i386/intel-pt: Define specific PT feature set for IceLake-server and Snowridge Xiaoyao Li
2022-12-09 7:11 ` Chenyi Qiang
2022-12-08 6:25 ` [PATCH v3 8/8] target/i386/intel-pt: Access MSR_IA32_RTIT_ADDRn based on guest CPUID configuration Xiaoyao Li
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=20221208062513.2589476-1-xiaoyao.li@intel.com \
--to=xiaoyao.li@intel.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).