From: Marc Zyngier <maz@kernel.org>
To: kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
kvm@vger.kernel.org
Cc: Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Oliver Upton <oliver.upton@linux.dev>,
Zenghui Yu <yuzenghui@huawei.com>,
Ganapatrao Kulkarni <gankulkarni@os.amperecomputing.com>
Subject: [PATCH 0/2] KVM: arm64: Make AArch64 support sticky
Date: Tue, 29 Apr 2025 12:41:15 +0100 [thread overview]
Message-ID: <20250429114117.3618800-1-maz@kernel.org> (raw)
It's been recently reported[1] that our sorry excuse for a test suite
is writing a bunch of zeroes to ID_AA64PFR0_EL1.EL{0,1,2,3},
effectively removing the advertised support for AArch64 to the guest.
This leads to an interesting interaction with the NV code which reacts
in a slightly overzealous way and inject an UNDEF at the earliest
opportunity.
This small series fixes KVM by bluntly refusing to disable AArch64,
and the test to stop being so lame. I'm also fixing the NV code
separately, since it isn't upstream.
[1] https://lore.kernel.org/r/4e63a13f-c5dc-4f97-879a-26b5548da07f@os.amperecomputing.com
Marc Zyngier (2):
KVM: arm64: Prevent userspace from disabling AArch64 support at any
virtualisable EL
KVM: arm64: selftest: Don't try to disable AArch64 support
arch/arm64/kvm/sys_regs.c | 6 ++++++
tools/testing/selftests/kvm/arm64/set_id_regs.c | 8 ++++----
2 files changed, 10 insertions(+), 4 deletions(-)
--
2.39.2
next reply other threads:[~2025-04-29 11:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 11:41 Marc Zyngier [this message]
2025-04-29 11:41 ` [PATCH 1/2] KVM: arm64: Prevent userspace from disabling AArch64 support at any virtualisable EL Marc Zyngier
2025-04-29 11:41 ` [PATCH 2/2] KVM: arm64: selftest: Don't try to disable AArch64 support Marc Zyngier
2025-04-30 5:38 ` [PATCH 0/2] KVM: arm64: Make AArch64 support sticky Ganapatrao Kulkarni
2025-05-07 7:56 ` Oliver Upton
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=20250429114117.3618800-1-maz@kernel.org \
--to=maz@kernel.org \
--cc=gankulkarni@os.amperecomputing.com \
--cc=joey.gouly@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=oliver.upton@linux.dev \
--cc=suzuki.poulose@arm.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