From: Wei Huang <wei@redhat.com>
To: kvm@vger.kernel.org
Cc: gleb@kernel.org, pbonzini@redhat.com, rkrcmar@redhat.com,
joro@8bytes.org
Subject: [PATCH V3 0/4] KVM vPMU support for AMD CPUs
Date: Sat, 18 Apr 2015 02:23:48 -0400 [thread overview]
Message-ID: <1429338232-11938-1-git-send-email-wei@redhat.com> (raw)
Currently KVM only supports vPMU for Intel CPUs. This patchset enables
KVM vPMU support for AMD platform by creating a common PMU interface for
x86. By refractoring, PMU related MSR accesses from guest VMs are dispatched
to corresponding functions defined in arch specific files.
V3:
* Rebase the code to the latest of KVM tree (queue branch);
* Branch out the Intel specific code from pmu.c to pmu_intel.c, in order
to reflect the change history more accurately;
* Name the parameters/variables more consistently (use msr, idx,
pmc_idx) across files;
* Fix issues (whitespaces, macro names, ...) based on Radim's V2 comments;
* Fix the MSR_K7_PERFCTRn and MSR_K7_EVNTSELn access code (in patch 4);
V2:
* Create a generic pmu.c file which is shared by Intel and AMD CPUs;
* pmu.c code becomes part of kvm.ko module. Similarly pmu_intel.c and
pmu_amd.c are linked to kvm-intel.ko and kvm-amd.ko respectively;
* Re-define kvm_pmu_ops function pointers. Per Radim Krcmar's comments,
a large portion of Intel vPMU code are now consolidated and moved to
pmu.c;
* Polish pmu_amd.c code to comply with new definition of kvm_pmu_ops;
V1:
* Adopt the file layout suggested by Radim Krcmar
* Link arch module with its specific PMU file
RFC:
* Initial version for RFC
Wei Huang (4):
KVM: x86/vPMU: Define kvm_pmu_ops to support vPMU function dispatch
KVM: x86/vPMU: Create vPMU interface for VMX and SVM
KVM: x86/vPMU: Implement AMD vPMU code for KVM
KVM: x86/vPMU: Enable PMU handling for AMD PERFCTRn and EVNTSELn MSRs
arch/x86/include/asm/kvm_host.h | 37 ++-
arch/x86/kvm/Makefile | 4 +-
arch/x86/kvm/cpuid.c | 3 +-
arch/x86/kvm/pmu.c | 557 +++++++++++-----------------------------
arch/x86/kvm/pmu.h | 98 +++++++
arch/x86/kvm/pmu_amd.c | 207 +++++++++++++++
arch/x86/kvm/pmu_intel.c | 359 ++++++++++++++++++++++++++
arch/x86/kvm/svm.c | 8 +
arch/x86/kvm/vmx.c | 8 +
arch/x86/kvm/x86.c | 47 ++--
10 files changed, 891 insertions(+), 437 deletions(-)
create mode 100644 arch/x86/kvm/pmu.h
create mode 100644 arch/x86/kvm/pmu_amd.c
create mode 100644 arch/x86/kvm/pmu_intel.c
--
1.8.3.1
next reply other threads:[~2015-04-18 6:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-18 6:23 Wei Huang [this message]
2015-04-18 6:23 ` [PATCH V3 1/4] KVM: x86/vPMU: Define kvm_pmu_ops to support vPMU function dispatch Wei Huang
2015-04-18 6:23 ` [PATCH V3 2/4] KVM: x86/vPMU: Create vPMU interface for VMX and SVM Wei Huang
2015-04-22 17:20 ` Radim Krčmář
2015-04-18 6:23 ` [PATCH V3 3/4] KVM: x86/vPMU: Implement AMD vPMU code for KVM Wei Huang
2015-04-22 17:22 ` Radim Krčmář
2015-04-18 6:23 ` [PATCH V3 4/4] KVM: x86/vPMU: Enable PMU handling for AMD PERFCTRn and EVNTSELn MSRs Wei Huang
2015-04-22 17:23 ` Radim Krčmář
2015-04-21 16:38 ` [PATCH V3 0/4] KVM vPMU support for AMD CPUs Radim Krčmář
2015-04-22 17:28 ` Radim Krčmář
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=1429338232-11938-1-git-send-email-wei@redhat.com \
--to=wei@redhat.com \
--cc=gleb@kernel.org \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--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