From: Oliver Upton <oupton@kernel.org>
To: Marc Zyngier <maz@kernel.org>,
kvmarm@lists.linux.dev, Karl Mehltretter <kmehltretter@gmail.com>
Cc: Joey Gouly <joey.gouly@arm.com>,
Steffen Eiden <seiden@linux.ibm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Fuad Tabba <fuad.tabba@linux.dev>
Subject: Re: [PATCH] KVM: arm64: Fix AArch32 DBGBXVR<n> handling
Date: Sat, 19 Sep 2026 11:16:21 -0700 [thread overview]
Message-ID: <aq7RdZqJNNtqmaQ7@kernel.org> (raw)
In-Reply-To: <178984145401.38162.12449211285441501967.b4-ty@kernel.org>
On Sat, Sep 19, 2026 at 11:11:14AM -0700, Oliver Upton wrote:
> On Mon, 10 Aug 2026 02:56:16 +0200, Karl Mehltretter wrote:
> > The consolidation of the breakpoint and watchpoint register accessors
> > switched DBGBXVR<n> from trap_bvr() to trap_dbg_wb_reg(). The latter
> > selects backing storage with demux_wb_reg(), which only handles Op2 values
> > 4 through 7. Since DBGBXVR<n> uses Op2 1, an AArch32 guest access hits
> > KVM_BUG_ON() and marks the VM dead.
> >
> > DBGBXVR<n> aliases DBGBVR<n>_EL1[63:32], and its AA32(HI) descriptor
> > already selects the upper half. Map Op2 1 to dbg_bvr[] alongside Op2 4,
> > restoring the pre-regression behavior.
> >
> > [...]
>
> Thanks for pinging, this slipped between the cracks.
>
> Applied to fixes, thanks!
>
> [1/1] KVM: arm64: Fix AArch32 DBGBXVR<n> handling
> https://git.kernel.org/kvmarm/kvmarm/c/239763bda716
This is now 6b1bca1b1ab7, didn't grab the Cc: stable in the first pass.
Thanks,
Oliver
prev parent reply other threads:[~2026-09-19 18:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 0:56 [PATCH] KVM: arm64: Fix AArch32 DBGBXVR<n> handling Karl Mehltretter
2026-08-10 8:52 ` Marc Zyngier
2026-09-19 5:18 ` Karl Mehltretter
2026-09-19 18:11 ` Oliver Upton
2026-09-19 18:16 ` 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=aq7RdZqJNNtqmaQ7@kernel.org \
--to=oupton@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=fuad.tabba@linux.dev \
--cc=joey.gouly@arm.com \
--cc=kmehltretter@gmail.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@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.