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, rananta@google.com,
tabba@google.com, arnd@arndb.de,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>
Subject: [GIT PULL] KVM/arm64 fixes for 6.5, part #2
Date: Tue, 1 Aug 2023 01:15:14 -0700 [thread overview]
Message-ID: <ZMi/EkSLgRymQZzN@thinky-boi> (raw)
Hi Paolo,
Second batch of fixes for 6.5 here. As usual, details are in the tag but
of particular interest is the fix for AmpereOne systems, as VMs fail to
boot when setting up the MMU (yikes).
Please pull.
--
Thanks,
Oliver
The following changes since commit 9d2a55b403eea26cab7c831d8e1c00ef1e6a6850:
KVM: arm64: Fix the name of sys_reg_desc related to PMU (2023-07-14 23:34:05 +0000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git tags/kvmarm-fixes-6.5-2
for you to fetch changes up to 74158a8cad79d2f5dcf71508993664c5cfcbfa3c:
KVM: arm64: Skip instruction after emulating write to TCR_EL1 (2023-07-28 17:11:23 +0000)
----------------------------------------------------------------
KVM/arm64 fixes for 6.5, part #2
- Fixes for the configuration of SVE/SME traps when hVHE mode is in use
- Allow use of pKVM on systems with FF-A implementations that are v1.0
compatible
- Request/release percpu IRQs (arch timer, vGIC maintenance) correctly
when pKVM is in use
- Fix function prototype after __kvm_host_psci_cpu_entry() rename
- Skip to the next instruction when emulating writes to TCR_EL1 on
AmpereOne systems
----------------------------------------------------------------
Arnd Bergmann (1):
KVM: arm64: fix __kvm_host_psci_cpu_entry() prototype
Fuad Tabba (7):
KVM: arm64: Factor out code for checking (h)VHE mode into a macro
KVM: arm64: Use the appropriate feature trap register for SVE at EL2 setup
KVM: arm64: Disable SME traps for (h)VHE at setup
KVM: arm64: Helper to write to appropriate feature trap register based on mode
KVM: arm64: Use the appropriate feature trap register when activating traps
KVM: arm64: Fix resetting SVE trap values on reset for hVHE
KVM: arm64: Fix resetting SME trap values on reset for (h)VHE
Oliver Upton (3):
KVM: arm64: Allow pKVM on v1.0 compatible FF-A implementations
KVM: arm64: Rephrase percpu enable/disable tracking in terms of hyp
KVM: arm64: Skip instruction after emulating write to TCR_EL1
Raghavendra Rao Ananta (1):
KVM: arm64: Fix hardware enable/disable flows for pKVM
arch/arm64/include/asm/el2_setup.h | 44 ++++++++++++++++--------
arch/arm64/include/asm/kvm_asm.h | 2 +-
arch/arm64/include/asm/kvm_emulate.h | 21 +++++++++---
arch/arm64/kvm/arm.c | 61 +++++++++++++++------------------
arch/arm64/kvm/hyp/include/hyp/switch.h | 1 +
arch/arm64/kvm/hyp/nvhe/ffa.c | 15 +++++++-
arch/arm64/kvm/hyp/nvhe/switch.c | 2 +-
7 files changed, 90 insertions(+), 56 deletions(-)
next reply other threads:[~2023-08-01 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 8:15 Oliver Upton [this message]
2023-08-04 17:39 ` [GIT PULL] KVM/arm64 fixes for 6.5, part #2 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=ZMi/EkSLgRymQZzN@thinky-boi \
--to=oliver.upton@linux.dev \
--cc=arnd@arndb.de \
--cc=james.morse@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=rananta@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