From: Oliver Upton <oliver.upton@linux.dev>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Marc Zyngier <maz@kernel.org>,
kvmarm@lists.linux.dev, kvm@vger.kernel.org,
Mark Brown <broonie@kernel.org>,
Quentin Perret <qperret@google.com>
Subject: [GIT PULL] Last KVM/arm64 fixes for 6.13
Date: Thu, 2 Jan 2025 14:20:30 -0800 [thread overview]
Message-ID: <Z3cRLtgqPUCvyrkj@linux.dev> (raw)
Hi Paolo,
A little slow on the draw with the last set of fixes because of the
holidays. Nothing particularly remarkable here given that both pKVM
and NV are in a half-baked state upstream, although the selftests fix
does plug a new test failure as of 6.13.
Please pull.
--
Thanks,
Oliver
The following changes since commit 78d4f34e2115b517bcbfe7ec0d018bbbb6f9b0b8:
Linux 6.13-rc3 (2024-12-15 15:58:23 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git/ tags/kvmarm-fixes-6.13-3
for you to fetch changes up to e96d8b80afd3f63ffad58c0fdd5e0c380c4c404e:
KVM: arm64: Only apply PMCR_EL0.P to the guest range of counters (2024-12-18 13:22:25 -0800)
----------------------------------------------------------------
KVM/arm64 changes for 6.13, part #3
- Always check page state in hyp_ack_unshare()
- Align set_id_regs selftest with the fact that ASIDBITS field is RO
- Various vPMU fixes for bugs that only affect nested virt
----------------------------------------------------------------
Mark Brown (1):
KVM: arm64: Fix set_id_regs selftest for ASIDBITS becoming unwritable
Oliver Upton (4):
KVM: arm64: Add unified helper for reprogramming counters by mask
KVM: arm64: Use KVM_REQ_RELOAD_PMU to handle PMCR_EL0.E change
KVM: arm64: nv: Reload PMU events upon MDCR_EL2.HPME change
KVM: arm64: Only apply PMCR_EL0.P to the guest range of counters
Quentin Perret (1):
KVM: arm64: Always check the state from hyp_ack_unshare()
arch/arm64/kvm/hyp/nvhe/mem_protect.c | 3 -
arch/arm64/kvm/pmu-emul.c | 89 +++++++++--------------
arch/arm64/kvm/sys_regs.c | 32 ++++++--
include/kvm/arm_pmu.h | 6 +-
tools/testing/selftests/kvm/aarch64/set_id_regs.c | 1 -
5 files changed, 62 insertions(+), 69 deletions(-)
reply other threads:[~2025-01-02 22:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Z3cRLtgqPUCvyrkj@linux.dev \
--to=oliver.upton@linux.dev \
--cc=broonie@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=qperret@google.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