From: Oliver Upton <oliver.upton@linux.dev>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Marc Zyngier <maz@kernel.org>, Fuad Tabba <tabba@google.com>,
Reiji Watanabe <reijiw@google.com>,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
kvmarm@lists.linux.dev, kvm@vger.kernel.org
Subject: [GIT PULL] KVM/arm64 fixes for 6.3, part #3
Date: Wed, 5 Apr 2023 09:12:49 -0700 [thread overview]
Message-ID: <ZC2eAXc9UE7Vesmn@thinky-boi> (raw)
Hi Paolo,
Sending out what is likely the last batch of fixes for 6.3. Most
noteworthy is the PMU fix, as Reiji found that events counting in guest
userspace stopped working after live migration on VHE systems.
Additionally, Fuad found that pKVM was underselling the Spectre/Meltdown
mitigation state to protected VMs, so we have a fix for that too.
Also, FYI, Marc will reprise his role for the 6.4 kernel. Nothing is
set in stone but the working model is that we'll alternate the
maintainer duties each kernel release.
Please pull,
Oliver
The following changes since commit 8c2e8ac8ad4be68409e806ce1cc78fc7a04539f3:
KVM: arm64: Check for kvm_vma_mte_allowed in the critical section (2023-03-16 23:42:56 +0000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git tags/kvmarm-fixes-6.3-3
for you to fetch changes up to e81625218bf7986ba1351a98c43d346b15601d26:
KVM: arm64: Advertise ID_AA64PFR0_EL1.CSV2/3 to protected VMs (2023-04-04 15:52:06 +0000)
----------------------------------------------------------------
KVM/arm64 fixes for 6.3, part #3
- Ensure the guest PMU context is restored before the first KVM_RUN,
fixing an issue where EL0 event counting is broken after vCPU
save/restore
- Actually initialize ID_AA64PFR0_EL1.{CSV2,CSV3} based on the
sanitized, system-wide values for protected VMs
----------------------------------------------------------------
Fuad Tabba (1):
KVM: arm64: Advertise ID_AA64PFR0_EL1.CSV2/3 to protected VMs
Reiji Watanabe (1):
KVM: arm64: PMU: Restore the guest's EL0 event counting after migration
arch/arm64/kvm/arm.c | 26 +++++++++++++++++++++++++-
arch/arm64/kvm/hyp/include/nvhe/fixed_config.h | 5 ++++-
arch/arm64/kvm/hyp/nvhe/sys_regs.c | 7 -------
arch/arm64/kvm/pmu-emul.c | 1 +
arch/arm64/kvm/sys_regs.c | 1 -
5 files changed, 30 insertions(+), 10 deletions(-)
next reply other threads:[~2023-04-05 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 16:12 Oliver Upton [this message]
2023-04-06 17:35 ` [GIT PULL] KVM/arm64 fixes for 6.3, part #3 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=ZC2eAXc9UE7Vesmn@thinky-boi \
--to=oliver.upton@linux.dev \
--cc=james.morse@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=reijiw@google.com \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.com \
--cc=yuzenghui@huawei.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