From: Oliver Upton <oupton@kernel.org>
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>,
Wei-Lin Chang <weilin.chang@arm.com>,
Steffen Eiden <seiden@linux.ibm.com>,
Oliver Upton <oupton@kernel.org>
Subject: [PATCH v3 0/5] KVM: arm64: nv: Even more VNCR fixes
Date: Thu, 18 Jun 2026 16:42:01 -0700 [thread overview]
Message-ID: <20260618234207.1063941-1-oupton@kernel.org> (raw)
Addressing most of the issues that came up with v2. Of note, I left
Sashiko's (valid) feedback about HWPOISON PFNs not signalling userspace
unaddressed because it requires untangling the return code mess a bit.
That and the bugs fixed in this series are quite a bit worse :)
Applies to kvmarm/fixes.
v2 -> v3:
- Avoid evaluating permissions in case of early return / higher
priority fault (Marc)
- Drop BUG_ON() from VNCR abort injetion path (Marc)
- Ensure is_gmem is always initialized (Sashiko)
- Return EINVAL for SEAs due to memory attribute mismatch, avoiding
confusion with gmem memory fault exits (Sashiko)
Oliver Upton (5):
KVM: arm64: nv: Respect read-only PFN when mapping L1 VNCR
KVM: arm64: nv: Inject SEA if kvm_translate_vncr() can't resolve PFN
KVM: arm64: nv: Re-translate VNCR before injecting abort
KVM: arm64: nv: Inject SEA if guest VNCR isn't normal memory
KVM: arm64: nv: Mark VM as bugged for unexpected VNCR abort
arch/arm64/include/asm/kvm_nested.h | 8 ++
arch/arm64/kvm/at.c | 8 --
arch/arm64/kvm/nested.c | 164 ++++++++++++++--------------
3 files changed, 91 insertions(+), 89 deletions(-)
base-commit: fcda30b134d262a1b1826555352bd7349051486e
--
2.47.3
next reply other threads:[~2026-06-18 23:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 23:42 Oliver Upton [this message]
2026-06-18 23:42 ` [PATCH v3 1/5] KVM: arm64: nv: Respect read-only PFN when mapping L1 VNCR Oliver Upton
2026-06-19 0:07 ` sashiko-bot
2026-06-18 23:42 ` [PATCH v3 2/5] KVM: arm64: nv: Inject SEA if kvm_translate_vncr() can't resolve PFN Oliver Upton
2026-06-18 23:57 ` sashiko-bot
2026-06-18 23:42 ` [PATCH v3 3/5] KVM: arm64: nv: Re-translate VNCR before injecting abort Oliver Upton
2026-06-19 0:00 ` sashiko-bot
2026-06-18 23:42 ` [PATCH v3 4/5] KVM: arm64: nv: Inject SEA if guest VNCR isn't normal memory Oliver Upton
2026-06-18 23:42 ` [PATCH v3 5/5] KVM: arm64: nv: Mark VM as bugged for unexpected VNCR abort 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=20260618234207.1063941-1-oupton@kernel.org \
--to=oupton@kernel.org \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=seiden@linux.ibm.com \
--cc=suzuki.poulose@arm.com \
--cc=weilin.chang@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 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.