From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Sean Christopherson <seanjc@google.com>
Subject: [GIT PULL] KVM: x86: PMU changes for 6.11
Date: Fri, 12 Jul 2024 16:56:56 -0700 [thread overview]
Message-ID: <20240712235701.1458888-7-seanjc@google.com> (raw)
In-Reply-To: <20240712235701.1458888-1-seanjc@google.com>
A small collection of PMU cleanups.
The following changes since commit c3f38fa61af77b49866b006939479069cd451173:
Linux 6.10-rc2 (2024-06-02 15:44:56 -0700)
are available in the Git repository at:
https://github.com/kvm-x86/linux.git tags/kvm-x86-pmu-6.11
for you to fetch changes up to f287bef6ddc208cae49c8d3833aeecda47872608:
KVM: x86/pmu: Introduce distinct macros for GP/fixed counter max number (2024-06-28 09:12:16 -0700)
----------------------------------------------------------------
KVM x86/pmu changes for 6.11
- Don't advertise IA32_PERF_GLOBAL_OVF_CTRL as an MSR-to-be-saved, as it reads
'0' and writes from userspace are ignored.
- Update to the newfangled Intel CPU FMS infrastructure.
- Use macros instead of open-coded literals to clean up KVM's manipulation of
FIXED_CTR_CTRL MSRs.
----------------------------------------------------------------
Dapeng Mi (3):
KVM: x86/pmu: Change ambiguous _mask suffix to _rsvd in kvm_pmu
KVM: x86/pmu: Manipulate FIXED_CTR_CTRL MSR with macros
KVM: x86/pmu: Introduce distinct macros for GP/fixed counter max number
Jim Mattson (1):
KVM: x86: Remove IA32_PERF_GLOBAL_OVF_CTRL from KVM_GET_MSR_INDEX_LIST
Sean Christopherson (1):
KVM: x86/pmu: Add a helper to enable bits in FIXED_CTR_CTRL
Tony Luck (2):
KVM: x86/pmu: Switch to new Intel CPU model defines
KVM: VMX: Switch to new Intel CPU model infrastructure
arch/x86/include/asm/kvm_host.h | 30 +++++++++++++-----------
arch/x86/kvm/pmu.c | 36 ++++++++++++++--------------
arch/x86/kvm/pmu.h | 10 ++++----
arch/x86/kvm/svm/pmu.c | 11 ++++-----
arch/x86/kvm/vmx/pmu_intel.c | 52 +++++++++++++++++++++++------------------
arch/x86/kvm/vmx/vmx.c | 20 +++++++---------
arch/x86/kvm/x86.c | 17 ++++++++------
7 files changed, 94 insertions(+), 82 deletions(-)
next prev parent reply other threads:[~2024-07-12 23:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 23:56 [GIT PULL] KVM: x86 pull requests for 6.11 Sean Christopherson
2024-07-12 23:56 ` [GIT PULL] KVM: x86: Single Xen fix for 6.10 or 6.11 Sean Christopherson
2024-07-12 23:56 ` [GIT PULL] KVM: Generic changes for 6.11 Sean Christopherson
2024-07-12 23:56 ` [GIT PULL] KVM: x86: Misc " Sean Christopherson
2024-07-12 23:56 ` [GIT PULL] KVM: x86: MMU " Sean Christopherson
2024-07-12 23:56 ` [GIT PULL] KVM: x86: Remove MTRR virtualization Sean Christopherson
2024-07-12 23:56 ` Sean Christopherson [this message]
2024-07-12 23:56 ` [GIT PULL] KVM: Selftests changes for 6.11 Sean Christopherson
2024-07-12 23:56 ` [GIT PULL (sort of)] KVM: x86: Static call " Sean Christopherson
2024-07-16 14:16 ` Paolo Bonzini
2024-07-16 15:46 ` Sean Christopherson
2024-07-17 5:52 ` Paolo Bonzini
2024-07-12 23:56 ` [GIT PULL] KVM: x86: SVM " Sean Christopherson
2024-07-12 23:57 ` [GIT PULL] KVM: x86: VMX " Sean Christopherson
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=20240712235701.1458888-7-seanjc@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@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