From: Will Deacon <will@kernel.org>
To: Vladimir Murzin <vladimir.murzin@arm.com>
Cc: Breno Leitao <leitao@debian.org>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Jinjie Ruan <ruanjinjie@huawei.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
rmikey@meta.com, kernel-team@meta.com,
Ada Couprie Diaz <ada.coupriediaz@arm.com>
Subject: Re: [PATCH RFC] arm64: entry: PSTATE_I_SET is leaking on pseudo NMI mode
Date: Tue, 11 Aug 2026 12:32:31 +0100 [thread overview]
Message-ID: <ansIT2PCHq_EKuTE@willie-the-truck> (raw)
In-Reply-To: <9b06f274-8db1-48e4-839e-e387c050d328@arm.com>
On Mon, Aug 10, 2026 at 05:39:52PM +0100, Vladimir Murzin wrote:
> On 8/10/26 16:05, Will Deacon wrote:
> > So we could probably hack something as you suggest, but maybe the best
> > option is to take patches 8 and 9 from your FEAT_NMI series? WDYT?
> >
>
> Whatever you prefer, tbh :)
>
> Patch 9 codifies my understanding of how things are expected to
> work. That said, I accept that I could be missing something, hence the
> RFC tag.
Those two look fine to me and I already took the preceding changes.
> In case you decide to take it, we probably need to:
>
> - extend the commit message to cover Breno's report (right now, the
> commit message makes it look like a refactoring)
>
> - add Fixes tags if we want it to be backported
>
> Alternatively, I can respin the patch separately with the suggestions
> above applied - just let me know ;)
Lemme have a go at picking them up... I'll yell if it all goes horribly
wrong!
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Vladimir Murzin <vladimir.murzin@arm.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
rmikey@meta.com,
"Peter Zijlstra \(Intel\)" <peterz@infradead.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Jinjie Ruan <ruanjinjie@huawei.com>,
kernel-team@meta.com, linux-kernel@vger.kernel.org,
Breno Leitao <leitao@debian.org>,
bpf@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RFC] arm64: entry: PSTATE_I_SET is leaking on pseudo NMI mode
Date: Tue, 11 Aug 2026 12:32:31 +0100 [thread overview]
Message-ID: <ansIT2PCHq_EKuTE@willie-the-truck> (raw)
In-Reply-To: <9b06f274-8db1-48e4-839e-e387c050d328@arm.com>
On Mon, Aug 10, 2026 at 05:39:52PM +0100, Vladimir Murzin wrote:
> On 8/10/26 16:05, Will Deacon wrote:
> > So we could probably hack something as you suggest, but maybe the best
> > option is to take patches 8 and 9 from your FEAT_NMI series? WDYT?
> >
>
> Whatever you prefer, tbh :)
>
> Patch 9 codifies my understanding of how things are expected to
> work. That said, I accept that I could be missing something, hence the
> RFC tag.
Those two look fine to me and I already took the preceding changes.
> In case you decide to take it, we probably need to:
>
> - extend the commit message to cover Breno's report (right now, the
> commit message makes it look like a refactoring)
>
> - add Fixes tags if we want it to be backported
>
> Alternatively, I can respin the patch separately with the suggestions
> above applied - just let me know ;)
Lemme have a go at picking them up... I'll yell if it all goes horribly
wrong!
Will
next prev parent reply other threads:[~2026-08-11 11:32 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 11:45 [PATCH RFC] arm64: entry: PSTATE_I_SET is leaking on pseudo NMI mode Breno Leitao
2026-08-07 13:40 ` Will Deacon
2026-08-07 13:40 ` Will Deacon
2026-08-07 13:57 ` Mark Rutland
2026-08-07 13:57 ` Mark Rutland
2026-08-07 14:49 ` Vladimir Murzin
2026-08-07 14:49 ` Vladimir Murzin
2026-08-10 12:44 ` Jinjie Ruan
2026-08-10 12:44 ` Jinjie Ruan
2026-08-10 13:04 ` Vladimir Murzin
2026-08-10 13:04 ` Vladimir Murzin
2026-08-11 2:47 ` Jinjie Ruan
2026-08-11 2:47 ` Jinjie Ruan
2026-08-11 8:18 ` Vladimir Murzin
2026-08-11 8:18 ` Vladimir Murzin
2026-08-07 14:58 ` Breno Leitao
2026-08-07 14:58 ` Breno Leitao
2026-08-07 16:29 ` Breno Leitao
2026-08-07 16:29 ` Breno Leitao
2026-08-10 11:43 ` Will Deacon
2026-08-10 11:43 ` Will Deacon
2026-08-10 12:42 ` Vladimir Murzin
2026-08-10 12:42 ` Vladimir Murzin
2026-08-10 15:05 ` Will Deacon
2026-08-10 15:05 ` Will Deacon
2026-08-10 16:39 ` Vladimir Murzin
2026-08-10 16:39 ` Vladimir Murzin
2026-08-11 11:32 ` Will Deacon [this message]
2026-08-11 11:32 ` Will Deacon
2026-08-11 12:08 ` Vladimir Murzin
2026-08-11 12:08 ` Vladimir Murzin
2026-08-10 12:51 ` Jinjie Ruan
2026-08-10 12:51 ` Jinjie Ruan
2026-08-10 12:59 ` Breno Leitao
2026-08-10 12:59 ` Breno Leitao
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=ansIT2PCHq_EKuTE@willie-the-truck \
--to=will@kernel.org \
--cc=ada.coupriediaz@arm.com \
--cc=bpf@vger.kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peterz@infradead.org \
--cc=rmikey@meta.com \
--cc=ruanjinjie@huawei.com \
--cc=vladimir.murzin@arm.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.