From: Marc Zyngier <maz@kernel.org>
To: Oliver Upton <oliver.upton@linux.dev>
Cc: kvmarm@lists.linux.dev, Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>
Subject: Re: [PATCH 0/2] KVM: arm64: nv: Fix SError injection at EL2
Date: Fri, 19 Sep 2025 10:58:13 +0100 [thread overview]
Message-ID: <875xdezruy.wl-maz@kernel.org> (raw)
In-Reply-To: <20250918164632.410404-1-oliver.upton@linux.dev>
On Thu, 18 Sep 2025 17:46:30 +0100,
Oliver Upton <oliver.upton@linux.dev> wrote:
>
> FEAT_NV2 keeps us out of the loop on changes to HCR_EL2. That really
> sucks when the guest hypervisor toggles bits that affect the hyp
> context, such as TGE and xMO.
>
> The architecture now allows an implementation to treat HCR_EL2.AMO as 1
> any time that HCR_EL2.{E2H,TGE} = {1, 0}, effectively allowing us to
> hide what would otherwise be a quality of emulation bug in SError
> injection.
Yup. Note that the same relaxation also applies to IMO/FMO (that's the
reason why this relaxation was originally introduced), but I don't
think we need to do anything on that front.
> Unfortunately there's nothing to be done for E2H0 VMs, although given
> the direction of the architecture the offending hypervisor should just
> get with the times...
I have no sympathy for these either. Eventually, they'll get on with
the program, or experience the fate of 32bit...
I'll drag this into 6.18.
Thanks,
M.
--
Jazz isn't dead. It just smells funny.
next prev parent reply other threads:[~2025-09-19 9:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 16:46 [PATCH 0/2] KVM: arm64: nv: Fix SError injection at EL2 Oliver Upton
2025-09-18 16:46 ` [PATCH 1/2] KVM: arm64: nv: Treat AMO as 1 when at EL2 and {E2H,TGE} = {1, 0} Oliver Upton
2025-09-18 16:46 ` [PATCH 2/2] [DO NOT SUBMIT] KVM: arm64: selftests: Test effective value of HCR_EL2.AMO Oliver Upton
2025-09-19 9:58 ` Marc Zyngier [this message]
2025-09-19 12:39 ` [PATCH 0/2] KVM: arm64: nv: Fix SError injection at EL2 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=875xdezruy.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--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;
as well as URLs for NNTP newsgroup(s).