From: Wei Wang <wei.w.wang@intel.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
pbonzini@redhat.com, ak@linux.intel.com
Cc: kan.liang@intel.com, peterz@infradead.org, mingo@redhat.com,
rkrcmar@redhat.com, like.xu@intel.com, wei.w.wang@intel.com
Subject: [PATCH v2 0/8] Guest LBR Enabling
Date: Thu, 6 Sep 2018 19:30:48 +0800 [thread overview]
Message-ID: <1536233456-12173-1-git-send-email-wei.w.wang@intel.com> (raw)
Last Branch Recording (LBR) is a performance monitor unit (PMU) feature
on Intel CPUs that captures branch related info. This patch series enables
this feature to KVM guests.
Here is a conclusion of the fundamental methods that we use:
1) the LBR feature is enabled per guest via QEMU setting of
KVM_CAP_X86_GUEST_LBR;
2) when the guest has the LBR feature, the LBR stack is passed through to
the guest for direct accesses;
3) When the guest uses the LBR feature with the user callstack mode, the
host will help save/resotre the LBR stack when the vCPU thread is
scheduled out/in.
Patches 1-5 implements the above 1) and 2), and patches 6-8 implements
the above 3).
ChangeLog:
v1->v2:
- add the per guest LBR capability, KVM_CAP_X86_GUEST_LBR;
- save/restore the LBR stack conditionally on the vCPU thread context
switching, instead of on VMX transitions;
- expose MSR_IA32_PERF_CAPABILITIES to the guest.
The first version was sent out long time ago, and can be referenced here:
https://lkml.org/lkml/2017/9/25/11 , and thanks for lots of the
suggestions from Paolo Bonzini and Andi Kleen.
Like Xu (2):
KVM: PMU: support to save/restore the guest lbr stack on vCPU
switching
perf/x86/intel/lbr: add the guest_lbr boolean to cpuc
Wei Wang (6):
perf/x86: add a function to get the lbr stack
KVM/x86: KVM_CAP_X86_GUEST_LBR
KVM/vmx: Pass through the lbr stack to a guest
KVM/x86: expose MSR_IA32_PERF_CAPABILITIES to the guest
KVM/x86: enable the guest to access the debugctl msr
perf/x86/intel/lbr: guest requesting KVM for lbr stack save/restore
arch/x86/events/intel/lbr.c | 54 +++++++++++++++++++++++++--
arch/x86/events/perf_event.h | 1 +
arch/x86/include/asm/kvm_host.h | 3 ++
arch/x86/include/asm/perf_event.h | 19 ++++++++++
arch/x86/include/uapi/asm/kvm_para.h | 2 +
arch/x86/kvm/cpuid.c | 5 ++-
arch/x86/kvm/pmu_intel.c | 71 +++++++++++++++++++++++++++++++++++-
arch/x86/kvm/vmx.c | 60 ++++++++++++++++++++++++++++++
arch/x86/kvm/x86.c | 18 +++------
include/uapi/linux/kvm.h | 1 +
10 files changed, 215 insertions(+), 19 deletions(-)
--
2.7.4
next reply other threads:[~2018-09-06 12:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 11:30 Wei Wang [this message]
2018-09-06 11:30 ` [PATCH v2 1/8] perf/x86: add a function to get the lbr stack Wei Wang
2018-09-07 3:28 ` Andi Kleen
2018-09-07 6:45 ` Wei Wang
2018-09-06 11:30 ` [PATCH v2 2/8] KVM/x86: KVM_CAP_X86_GUEST_LBR Wei Wang
2018-09-06 11:30 ` [PATCH v2 3/8] KVM/vmx: Pass through the lbr stack to a guest Wei Wang
2018-09-06 11:30 ` [PATCH v2 4/8] KVM/x86: expose MSR_IA32_PERF_CAPABILITIES to the guest Wei Wang
2018-09-06 11:30 ` [PATCH v2 5/8] KVM/x86: enable the guest to access the debugctl msr Wei Wang
2018-09-06 11:30 ` [PATCH v2 6/8] perf/x86/intel/lbr: guest requesting KVM for lbr stack save/restore Wei Wang
2018-09-07 3:27 ` Andi Kleen
2018-09-07 5:24 ` Wei Wang
2018-09-07 14:10 ` Andi Kleen
2018-09-07 15:20 ` Wang, Wei W
2018-09-07 20:05 ` Andi Kleen
2018-09-08 1:34 ` Wang, Wei W
2018-09-06 11:30 ` [PATCH v2 7/8] KVM: PMU: support to save/restore the guest lbr stack on vCPU switching Wei Wang
2018-09-07 14:36 ` Jann Horn
2018-09-07 15:21 ` Wang, Wei W
2018-09-18 0:58 ` Gonglei (Arei)
2018-09-18 2:56 ` Andi Kleen
2018-09-18 9:57 ` Wei Wang
2018-09-18 10:34 ` Gonglei (Arei)
2018-09-06 11:30 ` [PATCH v2 8/8] perf/x86/intel/lbr: add the guest_lbr boolean to cpuc Wei Wang
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=1536233456-12173-1-git-send-email-wei.w.wang@intel.com \
--to=wei.w.wang@intel.com \
--cc=ak@linux.intel.com \
--cc=kan.liang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=like.xu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rkrcmar@redhat.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).