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, peterz@infradead.org
Cc: kan.liang@intel.com, mingo@redhat.com, rkrcmar@redhat.com,
like.xu@intel.com, wei.w.wang@intel.com, jannh@google.com,
arei.gonglei@huawei.com
Subject: [PATCH v4 00/10] Guest LBR Enabling
Date: Wed, 26 Dec 2018 17:25:28 +0800 [thread overview]
Message-ID: <1545816338-1171-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) the LBR stack is passed through to the guest for direct accesses after
the guest's first access to any of the lbr related MSRs;
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 is scheduled
out/in.
ChangeLog:
v3->v4:
- perf/x86:
- Patch 1: change the lbr msr variable type to "unsigned int";
- Patch 6: add a "no_counter" boolean attr to let callers
explicitly tell the perf core to not allocate counters for the
event;
- Patch 7: change "cpuc->vcpu_lbr" from "boolean" to "u8", and add
the PF_VCPU and is_kernel_event checks befoer setting it;
- Patch 8: add the LBR_SELECT save/restore on vCPU switching;
- Patch 9: move lbr_select_user_callstack to .h, instead of
exporting it;
- KVM/x86:
- Patch 3: use "cap->args[0]" to enable/disable the lbr feature
from userspace;
- Patch 4: forbid the enabling the guest lbr when the host and
guest see different lbr stack entries;
- Patch 10: in guest_access_lbr_msr, pass through the lbr stack
only when it has been passed through (i.e. add the check
!vcpu->arch.lbr_used).
previous:
https://lkml.org/lkml/2018/9/20/507
Like Xu (1):
KVM/x86/vPMU: Add APIs to support host save/restore the guest lbr
stack
Wei Wang (9):
perf/x86: fix the variable type of the LBR MSRs
perf/x86: add a function to get the lbr stack
KVM/x86: KVM_CAP_X86_GUEST_LBR
KVM/x86: intel_pmu_lbr_enable
KVM/x86: expose MSR_IA32_PERF_CAPABILITIES to the guest
perf/x86: no counter allocation support
perf/x86: save/restore LBR_SELECT on vCPU switching
perf/x86: function to check lbr user callstack mode
KVM/x86/lbr: lazy save the guest lbr stack
arch/x86/events/core.c | 12 +++
arch/x86/events/intel/lbr.c | 82 ++++++++---------
arch/x86/events/perf_event.h | 6 +-
arch/x86/include/asm/kvm_host.h | 7 ++
arch/x86/include/asm/perf_event.h | 64 +++++++++++++
arch/x86/kvm/cpuid.c | 2 +-
arch/x86/kvm/cpuid.h | 8 ++
arch/x86/kvm/pmu.c | 8 ++
arch/x86/kvm/pmu.h | 10 +++
arch/x86/kvm/pmu_intel.c | 183 ++++++++++++++++++++++++++++++++++++++
arch/x86/kvm/vmx.c | 147 ++++++++++++++++++++++++++++++
arch/x86/kvm/x86.c | 14 +++
include/linux/perf_event.h | 12 +++
include/uapi/linux/kvm.h | 1 +
include/uapi/linux/perf_event.h | 3 +-
kernel/events/core.c | 7 --
16 files changed, 514 insertions(+), 52 deletions(-)
--
2.7.4
next reply other threads:[~2018-12-26 9:25 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-26 9:25 Wei Wang [this message]
2018-12-26 9:25 ` [PATCH v4 01/10] perf/x86: fix the variable type of the LBR MSRs Wei Wang
2018-12-26 9:25 ` [PATCH v4 02/10] perf/x86: add a function to get the lbr stack Wei Wang
2018-12-26 9:25 ` [PATCH v4 03/10] KVM/x86: KVM_CAP_X86_GUEST_LBR Wei Wang
2018-12-26 9:25 ` [PATCH v4 04/10] KVM/x86: intel_pmu_lbr_enable Wei Wang
2019-01-02 16:33 ` Liang, Kan
2019-01-04 9:58 ` Wei Wang
2019-01-04 15:57 ` Liang, Kan
2019-01-05 10:09 ` Wei Wang
2019-01-07 14:22 ` Liang, Kan
2019-01-08 6:13 ` Wei Wang
2019-01-08 14:08 ` Liang, Kan
2019-01-09 1:54 ` Wei Wang
2019-01-02 23:26 ` Jim Mattson
2019-01-03 7:22 ` Wei Wang
2019-01-03 15:34 ` Jim Mattson
2019-01-03 17:18 ` Andi Kleen
2019-01-04 10:09 ` Wei Wang
2019-01-04 15:53 ` Jim Mattson
2019-01-05 10:15 ` Wang, Wei W
2018-12-26 9:25 ` [PATCH v4 05/10] KVM/x86: expose MSR_IA32_PERF_CAPABILITIES to the guest Wei Wang
2019-01-02 23:40 ` Jim Mattson
2019-01-03 8:00 ` Wei Wang
2019-01-03 15:25 ` Jim Mattson
2019-01-07 9:15 ` Wei Wang
2019-01-07 18:05 ` Jim Mattson
2019-01-07 18:20 ` Andi Kleen
2019-01-07 18:48 ` Jim Mattson
2019-01-07 20:14 ` Andi Kleen
2019-01-07 21:00 ` Jim Mattson
2019-01-08 7:53 ` Wei Wang
2019-01-08 17:19 ` Jim Mattson
2018-12-26 9:25 ` [PATCH v4 06/10] perf/x86: no counter allocation support Wei Wang
2018-12-26 9:25 ` [PATCH v4 07/10] KVM/x86/vPMU: Add APIs to support host save/restore the guest lbr stack Wei Wang
2018-12-26 9:25 ` [PATCH v4 08/10] perf/x86: save/restore LBR_SELECT on vCPU switching Wei Wang
2018-12-26 9:25 ` [PATCH v4 09/10] perf/x86: function to check lbr user callstack mode Wei Wang
2018-12-26 9:25 ` [PATCH v4 10/10] KVM/x86/lbr: lazy save the guest lbr stack Wei Wang
2018-12-27 20:51 ` Andi Kleen
2018-12-28 3:47 ` Wei Wang
2018-12-28 19:10 ` Andi Kleen
2018-12-27 20:52 ` [PATCH v4 10/10] KVM/x86/lbr: lazy save the guest lbr stack II Andi Kleen
2018-12-29 4:25 ` Wang, Wei W
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=1545816338-1171-1-git-send-email-wei.w.wang@intel.com \
--to=wei.w.wang@intel.com \
--cc=ak@linux.intel.com \
--cc=arei.gonglei@huawei.com \
--cc=jannh@google.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