From: Mark Brown <broonie@kernel.org>
To: Marc Zyngier <maz@kernel.org>
Cc: Fuad Tabba <fuad.tabba@linux.dev>,
Oliver Upton <oupton@kernel.org>,
kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
Joey Gouly <joey.gouly@arm.com>,
Steffen Eiden <seiden@linux.ibm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Lorenzo Stoakes <ljs@kernel.org>, Fuad Tabba <tabba@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] KVM: arm64: Sanitise ID_AA64MMFR3_EL1.S1P[IO]E
Date: Wed, 21 Oct 2026 15:19:41 +0100 [thread overview]
Message-ID: <atjJ_WuM_6GuLkmI@sirena.org.uk> (raw)
In-Reply-To: <86mrs7ywsc.wl-maz@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 864 bytes --]
On Wed, Oct 21, 2026 at 03:04:51PM +0100, Marc Zyngier wrote:
> Mark Brown <broonie@kernel.org> wrote:
> > It would be nice to have it be more obvious to the VMM and/or it's users
> > that it messed up, as things stand features it thought it had set will
> > just silently vanish from the guest - they'd need to know that this is
> > something that might happen and check after finalization or similar.
> > That's probably more a documentation/education thing than anything for
> > the patch.
> The VMM is an integral part of implementing the architecture. If the
> VMM doesn't cooperate, that's its problem.
Absolutely, it's a bug if the VMM is doing this. What I'm saying is
that it could be helpful if the bug was made visible, with the silent
fixup VMM bugs could easily lurk around for longer before someone
notices the problem than they might otherwise.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-10-21 14:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 6:43 Fuad Tabba
2026-10-20 11:35 ` Lorenzo Stoakes (ARM)
2026-10-20 19:30 ` Fuad Tabba
2026-10-21 13:28 ` Lorenzo Stoakes (ARM)
2026-10-21 14:03 ` Marc Zyngier
2026-10-21 15:01 ` Lorenzo Stoakes (ARM)
2026-10-21 13:02 ` Mark Brown
2026-10-21 14:04 ` Marc Zyngier
2026-10-21 14:19 ` Mark Brown [this message]
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=atjJ_WuM_6GuLkmI@sirena.org.uk \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=fuad.tabba@linux.dev \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=seiden@linux.ibm.com \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.com \
--cc=will@kernel.org \
--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
all inboxes | Powered by JetHome®