From: Oliver Upton <oliver.upton@linux.dev>
To: kvmarm@lists.linux.dev, Oliver Upton <oliver.upton@linux.dev>
Cc: Marc Zyngier <maz@kernel.org>, 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: Fix + test for SError ESR
Date: Wed, 9 Jul 2025 09:59:51 -0700 [thread overview]
Message-ID: <175208038505.2014187.17969325052997297935.b4-ty@linux.dev> (raw)
In-Reply-To: <20250708230632.1954240-1-oliver.upton@linux.dev>
On Tue, 08 Jul 2025 16:06:30 -0700, Oliver Upton wrote:
> VSESR_EL2 only provides an ESR_EL1.ISS value for the SError, not a
> complete ESR. Namely, hardware sets the EC field to indicate an SError
> (0x2F), meaning we need to do the same for our software-emulated SError
> injection.
>
> Note that this behavior already exists for nested SError injection in
> kvm_inject_nested_serror(). I also extended the external_aborts test to
> assert the guest sees an expected ESR value for an SError.
>
> [...]
Applied to next, thanks!
[1/2] KVM: arm64: Populate ESR_ELx.EC for emulated SError injection
https://git.kernel.org/kvmarm/kvmarm/c/f6e2262dfa1a
[2/2] KVM: arm64: selftests: Test ESR propagation for vSError injection
https://git.kernel.org/kvmarm/kvmarm/c/f9e4e0a663d2
--
Best,
Oliver
prev parent reply other threads:[~2025-07-09 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 23:06 [PATCH 0/2] KVM: arm64: Fix + test for SError ESR Oliver Upton
2025-07-08 23:06 ` [PATCH 1/2] KVM: arm64: Populate ESR_ELx.EC for emulated SError injection Oliver Upton
2025-07-08 23:06 ` [PATCH 2/2] KVM: arm64: selftests: Test ESR propagation for vSError injection Oliver Upton
2025-07-09 16:59 ` Oliver Upton [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=175208038505.2014187.17969325052997297935.b4-ty@linux.dev \
--to=oliver.upton@linux.dev \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--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