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 fixes for 6.6
Date: Fri, 13 Oct 2023 16:48:07 -0700 [thread overview]
Message-ID: <20231013234808.1115781-1-seanjc@google.com> (raw)
Please pull three PMU fixes for 6.6. These aren't super urgent and have all
existed from some time, i.e. don't absolutely need to go into 6.6, but I also
don't see a good reason to hold them back (they're all tagged for stable, so
it's kind of a moot point).
The following changes since commit 5804c19b80bf625c6a9925317f845e497434d6d3:
Merge tag 'kvm-riscv-fixes-6.6-1' of https://github.com/kvm-riscv/linux into HEAD (2023-09-23 05:35:55 -0400)
are available in the Git repository at:
https://github.com/kvm-x86/linux.git tags/kvm-x86-pmu-6.6-fixes
for you to fetch changes up to 73554b29bd70546c1a9efc9c160641ef1b849358:
KVM: x86/pmu: Synthesize at most one PMI per VM-exit (2023-09-25 14:42:52 -0700)
----------------------------------------------------------------
KVM x86/pmu fixes for 6.6:
- Truncate writes to PMU counters to the counter's width to avoid spurious
overflows when emulating counter events in software.
- Set the LVTPC entry mask bit when handling a PMI (to match Intel-defined
architectural behavior).
- Treat KVM_REQ_PMI as a wake event instead of queueing host IRQ work to
kick the guest out of emulated halt.
----------------------------------------------------------------
Jim Mattson (2):
KVM: x86: Mask LVTPC when handling a PMI
KVM: x86/pmu: Synthesize at most one PMI per VM-exit
Roman Kagan (1):
KVM: x86/pmu: Truncate counter value to allowed width on write
arch/x86/include/asm/kvm_host.h | 1 -
arch/x86/kvm/lapic.c | 8 ++++++--
arch/x86/kvm/pmu.c | 27 +--------------------------
arch/x86/kvm/pmu.h | 6 ++++++
arch/x86/kvm/svm/pmu.c | 2 +-
arch/x86/kvm/vmx/pmu_intel.c | 4 ++--
arch/x86/kvm/x86.c | 3 +++
7 files changed, 19 insertions(+), 32 deletions(-)
next reply other threads:[~2023-10-13 23:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 23:48 Sean Christopherson [this message]
2023-10-13 23:48 ` [GIT PULL] KVM: x86: Selftests " Sean Christopherson
2023-10-15 12:25 ` Paolo Bonzini
2023-10-15 12:24 ` [GIT PULL] KVM: x86: PMU " Paolo Bonzini
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=20231013234808.1115781-1-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
all inboxes | Powered by JetHome®