From: Dan Carpenter <dan@pereq.eu>
To: Marc Zyngier <maz@kernel.org>
Cc: "Catalin Marinas" <catalin.marinas@arm.com>,
"Fuad Tabba" <fuad.tabba@linux.dev>,
"Joey Gouly" <joey.gouly@arm.com>,
kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
"Mark Rutland" <mark.rutland@arm.com>,
"Oliver Upton" <oupton@kernel.org>,
"Steffen Eiden" <seiden@linux.ibm.com>,
"Suzuki K Poulose" <suzuki.poulose@arm.com>,
"Will Deacon" <will@kernel.org>,
"Zenghui Yu" <yuzenghui@huawei.com>,
"Karthik Bhargavan" <karthik@pereq.eu>,
"Clément Blaudeau" <clement@cryspen.com>
Subject: [PATCH 0/3] KVM: arm64: nv: trap forwarding bugs
Date: Wed, 18 Nov 2026 18:29:39 +0300 [thread overview]
Message-ID: <cover.1795014776.git.dan@pereq.eu> (raw)
This was detected as part of our Formal Analysis work at Pereq.
Regular KVM and nested virt traps have been getting out of sync. Fix a
couple bugs and add a boot time check to prevent future bugs.
Dan Carpenter (3):
KVM: arm64: nv: Forward PIR_EL2, PIRE0_EL2 and POR_EL2 traps
KVM: arm64: nv: Forward CNTP_TVAL_EL02 and CNTV_TVAL_EL02 traps
KVM: arm64: nv: Report EL2 registers with no trap forwarding
arch/arm64/include/asm/kvm_host.h | 2 +-
arch/arm64/kvm/emulate-nested.c | 10 +++++++++-
arch/arm64/kvm/sys_regs.c | 23 +++++++++++++++++++++--
3 files changed, 31 insertions(+), 4 deletions(-)
--
2.53.0
next reply other threads:[~2026-11-18 15:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 15:29 Dan Carpenter [this message]
2026-11-18 15:29 ` [PATCH 1/3] KVM: arm64: nv: Forward PIR_EL2, PIRE0_EL2 and POR_EL2 traps Dan Carpenter
2026-11-18 15:30 ` [PATCH 2/3] KVM: arm64: nv: Forward CNTP_TVAL_EL02 and CNTV_TVAL_EL02 traps Dan Carpenter
2026-11-18 15:30 ` [PATCH 3/3] KVM: arm64: nv: Report EL2 registers with no trap forwarding Dan Carpenter
2026-11-19 12:43 ` [PATCH 0/3] KVM: arm64: nv: trap forwarding bugs 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=cover.1795014776.git.dan@pereq.eu \
--to=dan@pereq.eu \
--cc=catalin.marinas@arm.com \
--cc=clement@cryspen.com \
--cc=fuad.tabba@linux.dev \
--cc=joey.gouly@arm.com \
--cc=karthik@pereq.eu \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=seiden@linux.ibm.com \
--cc=suzuki.poulose@arm.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.