From: Marc Zyngier <maz@kernel.org>
To: Mark Brown <broonie@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:04:51 +0100 [thread overview]
Message-ID: <86mrs7ywsc.wl-maz@kernel.org> (raw)
In-Reply-To: <ati3_lymW0zaBsSU@sirena.co.uk>
On Wed, 21 Oct 2026 14:02:54 +0100,
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.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2026-10-21 14:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 6:43 [PATCH v3] KVM: arm64: Sanitise ID_AA64MMFR3_EL1.S1P[IO]E 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 18:37 ` Fuad Tabba
2026-10-21 13:02 ` Mark Brown
2026-10-21 14:04 ` Marc Zyngier [this message]
2026-10-21 14:19 ` Mark Brown
2026-10-26 12:01 ` Marc Zyngier
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=86mrs7ywsc.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.