From: Oliver Upton <oliver.upton@linux.dev>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Marc Zyngier <maz@kernel.org>,
kvm@vger.kernel.org, kvmarm@lists.linux.dev,
Catalin Marinas <catalin.marinas@arm.com>
Subject: [GIT PULL] KVM/arm64 fixes for 6.15, round #2
Date: Fri, 18 Apr 2025 14:01:58 -0700 [thread overview]
Message-ID: <aAK9xg9DMfCsCPux@linux.dev> (raw)
Hi Paolo,
Here's a single rather urgent fix for 6.15 that addresses boot failures
from the PV MIDR infrastructure. Catalin has reviewed the patch and
asked I grab it since it's the end of the working week for him.
Please pull.
Thanks,
Oliver
The following changes since commit a344e258acb0a7f0e7ed10a795c52d1baf705164:
KVM: arm64: Use acquire/release to communicate FF-A version negotiation (2025-04-07 15:03:34 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git/ tags/kvmarm-fixes-6.15-2
for you to fetch changes up to 117c3b21d3c79af56750f18a54f2c468f30c8a45:
arm64: Rework checks for broken Cavium HW in the PI code (2025-04-18 13:51:07 -0700)
----------------------------------------------------------------
KVM/arm64 fixes for 6.15, round #2
- Single fix for broken usage of 'multi-MIDR' infrastructure in PI
code, adding an open-coded erratum check for everyone's favorite pile
of sand: Cavium ThunderX
----------------------------------------------------------------
Marc Zyngier (1):
arm64: Rework checks for broken Cavium HW in the PI code
arch/arm64/include/asm/mmu.h | 11 -----------
arch/arm64/kernel/cpu_errata.c | 2 +-
arch/arm64/kernel/image-vars.h | 4 ----
arch/arm64/kernel/pi/map_kernel.c | 25 ++++++++++++++++++++++++-
4 files changed, 25 insertions(+), 17 deletions(-)
next reply other threads:[~2025-04-18 21:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 21:01 Oliver Upton [this message]
2025-04-24 17:36 ` [GIT PULL] KVM/arm64 fixes for 6.15, round #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=aAK9xg9DMfCsCPux@linux.dev \
--to=oliver.upton@linux.dev \
--cc=catalin.marinas@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=maz@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