Linux KVM/arm64 development list
 help / color / mirror / Atom feed
From: Oliver Upton <oliver.upton@linux.dev>
To: kvmarm@lists.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>,
	Oliver Upton <oliver.upton@linux.dev>
Subject: [PATCH 0/2] KVM: arm64: Fix + test for SError ESR
Date: Tue,  8 Jul 2025 16:06:30 -0700	[thread overview]
Message-ID: <20250708230632.1954240-1-oliver.upton@linux.dev> (raw)

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.

Oliver Upton (2):
  KVM: arm64: Populate ESR_ELx.EC for emulated SError injection
  KVM: arm64: selftests: Test ESR propagation for vSError injection

 arch/arm64/kvm/inject_fault.c                 |  4 +++
 .../selftests/kvm/arm64/external_aborts.c     | 32 +++++++++++++++++--
 2 files changed, 34 insertions(+), 2 deletions(-)


base-commit: 3c5832f03f2ecd2b881f5bfbae06feeead432c16
-- 
2.39.5


             reply	other threads:[~2025-07-08 23:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-08 23:06 Oliver Upton [this message]
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 ` [PATCH 0/2] KVM: arm64: Fix + test for SError ESR 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=20250708230632.1954240-1-oliver.upton@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