From: Yang Weijiang <weijiang.yang@intel.com>
To: pbonzini@redhat.com, ehabkost@redhat.com, mtosatti@redhat.com,
richard.henderson@linaro.org, qemu-devel@nongnu.org,
kvm@vger.kernel.org, likexu@tencent.com, wei.w.wang@intel.com
Cc: weijiang.yang@intel.com
Subject: [PATCH v5 0/2] Enable legacy LBR support for guest
Date: Sun, 23 Jan 2022 00:11:59 +0800 [thread overview]
Message-ID: <20220122161201.73528-1-weijiang.yang@intel.com> (raw)
KVM legacy LBR patches have been merged in kernel 5.12, this patchset
is to expose the feature to guest from the perf capability MSR. Qemu can
add LBR format in cpu option to achieve it, e.g., -cpu host,lbr-fmt=0x5,
the format should match host value in IA32_PERF_CAPABILITIES.
Note, KVM legacy LBR solution accelerates guest perf performace by LBR MSR
passthrough so it requires guest cpu model matches that of host's, i.e.,
only -cpu host is supported.
Change in v5:
1. This patchset is rebased on tip : 6621441db5
2. No functional change since v4.
Yang Weijiang (2):
qdev-properties: Add a new macro with bitmask check for uint64_t
property
target/i386: Add lbr-fmt vPMU option to support guest LBR
hw/core/qdev-properties.c | 19 +++++++++++++++++
include/hw/qdev-properties.h | 12 +++++++++++
target/i386/cpu.c | 40 ++++++++++++++++++++++++++++++++++++
target/i386/cpu.h | 10 +++++++++
4 files changed, 81 insertions(+)
--
2.27.0
next reply other threads:[~2022-01-22 8:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 16:11 Yang Weijiang [this message]
2022-01-22 16:12 ` [PATCH v5 1/2] qdev-properties: Add a new macro with bitmask check for uint64_t property Yang Weijiang
2022-01-22 16:12 ` [PATCH v5 2/2] target/i386: Add lbr-fmt vPMU option to support guest LBR Yang Weijiang
2022-02-09 9:14 ` [PATCH v5 0/2] Enable legacy LBR support for guest Like Xu
2022-02-10 0:37 ` Yang, Weijiang
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=20220122161201.73528-1-weijiang.yang@intel.com \
--to=weijiang.yang@intel.com \
--cc=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=likexu@tencent.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=wei.w.wang@intel.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).