From: Will Deacon <will@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
tglx@linutronix.de, peterz@infradead.org, mingo@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] arm64: fix lockdep in NMI context
Date: Thu, 23 Jun 2022 20:31:41 +0100 [thread overview]
Message-ID: <165599516275.2981885.2147188564179543777.b4-ty@kernel.org> (raw)
In-Reply-To: <20220511131733.4074499-1-mark.rutland@arm.com>
On Wed, 11 May 2022 14:17:31 +0100, Mark Rutland wrote:
> For lockdep to function correctly in NMI context, architectures need to
> correctly save/restore lockdep state at NMI entry/exit time, correctly
> manage lockdep state within the NMI context, and need to select
> TRACE_IRQFLAGS_NMI_SUPPORT.
>
> Currently arm64 falls short of this merely by failing to select
> TRACE_IRQFLAGS_NMI_SUPPORT, and this can result in spurious lockdep
> splats with GICv3 Pseudo-NMIs are in use. Patch 2 has an example.
>
> [...]
This looks good to me and the x86 changes are trivial (famous last
words...), so I've queued the series up on its own branch in the arm64
tree.
Applied to arm64 (for-next/irqflags-nmi), thanks!
[1/2] arch: make TRACE_IRQFLAGS_NMI_SUPPORT generic
https://git.kernel.org/arm64/c/4510bffb4d02
[2/2] arm64: select TRACE_IRQFLAGS_NMI_SUPPORT
https://git.kernel.org/arm64/c/3381da254fab
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2022-06-23 19:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 13:17 Mark Rutland
2022-05-11 13:17 ` [PATCH 1/2] arch: make TRACE_IRQFLAGS_NMI_SUPPORT generic Mark Rutland
2022-05-11 13:17 ` [PATCH 2/2] arm64: select TRACE_IRQFLAGS_NMI_SUPPORT Mark Rutland
2022-06-23 19:31 ` Will Deacon [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=165599516275.2981885.2147188564179543777.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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
Powered by JetHome