Rust for Linux List
 help / color / mirror / Atom feed
From: Joel Fernandes <joelagnelf@nvidia.com>
To: Boqun Feng <boqun@kernel.org>
Cc: "Steven Rostedt" <rostedt@goodmis.org>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Catalin Marinas" <catalin.marinas@arm.com>,
	"Will Deacon" <will@kernel.org>,
	"Jonas Bonn" <jonas@southpole.se>,
	"Stefan Kristiansson" <stefan.kristiansson@saunalahti.fi>,
	"Stafford Horne" <shorne@gmail.com>,
	"Heiko Carstens" <hca@linux.ibm.com>,
	"Vasily Gorbik" <gor@linux.ibm.com>,
	"Alexander Gordeev" <agordeev@linux.ibm.com>,
	"Christian Borntraeger" <borntraeger@linux.ibm.com>,
	"Sven Schnelle" <svens@linux.ibm.com>,
	"Thomas Gleixner" <tglx@kernel.org>,
	"Ingo Molnar" <mingo@redhat.com>,
	"Borislav Petkov" <bp@alien8.de>,
	"Dave Hansen" <dave.hansen@linux.intel.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>, "Arnd Bergmann" <arnd@arndb.de>,
	"Juri Lelli" <juri.lelli@redhat.com>,
	"Vincent Guittot" <vincent.guittot@linaro.org>,
	"Dietmar Eggemann" <dietmar.eggemann@arm.com>,
	"Ben Segall" <bsegall@google.com>, "Mel Gorman" <mgorman@suse.de>,
	"Valentin Schneider" <vschneid@redhat.com>,
	"K Prateek Nayak" <kprateek.nayak@amd.com>,
	"Waiman Long" <longman@redhat.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Miguel Ojeda" <ojeda@kernel.org>, "Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Jinjie Ruan" <ruanjinjie@huawei.com>,
	"Ada Couprie Diaz" <ada.coupriediaz@arm.com>,
	"Lyude Paul" <lyude@redhat.com>,
	"Sohil Mehta" <sohil.mehta@intel.com>,
	"Pawan Gupta" <pawan.kumar.gupta@linux.intel.com>,
	"Xin Li" <xin@zytor.com>,
	"Sean Christopherson" <seanjc@google.com>,
	"Nikunj A Dadhania" <nikunj@amd.com>,
	"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
	"Randy Dunlap" <rdunlap@infradead.org>,
	"Yury Norov" <ynorov@nvidia.com>,
	"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-openrisc@vger.kernel.org" <linux-openrisc@vger.kernel.org>,
	"linux-s390@vger.kernel.org" <linux-s390@vger.kernel.org>,
	"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
	"rust-for-linux@vger.kernel.org" <rust-for-linux@vger.kernel.org>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Joel Fernandes" <joelaf@google.com>
Subject: Re: [PATCH 02/11] preempt: Track NMI nesting to separate per-CPU counter
Date: Tue, 12 May 2026 23:33:55 +0000	[thread overview]
Message-ID: <AEF2F57C-4120-4F2E-9063-EF314F787104@nvidia.com> (raw)
In-Reply-To: <agOm0iiqrqPWXQPO@tardis.local>



> On May 12, 2026, at 6:16 PM, Boqun Feng <boqun@kernel.org> wrote:
> 
> On Tue, May 12, 2026 at 03:22:39PM -0400, Joel Fernandes wrote:
>> 
>> 
>>> On 5/12/2026 12:30 PM, Steven Rostedt wrote:
>>> On Thu,  7 May 2026 21:21:02 -0700
>>> Boqun Feng <boqun@kernel.org> wrote:
>>> 
>>>> From: Joel Fernandes <joelagnelf@nvidia.com>
>>>> 
>>>> Move NMI nesting tracking from the preempt_count bits to a separate per-CPU
>>>> counter (nmi_nesting). This is to free up the NMI bits in the preempt_count,
>>>> allowing those bits to be repurposed for other uses.  This also has the benefit
>>>> of tracking more than 16-levels deep if there is ever a need.
>>>> 
>>>> Reduce multiple bits in preempt_count for NMI tracking. Reduce NMI_BITS
>>>> from 3 to 1, using it only to detect if we're in an NMI.
>>>> 
>>>> Suggested-by: Boqun Feng <boqun.feng@gmail.com>
>>>> Signed-off-by: Joel Fernandes <joelaf@google.com>
>>>> Signed-off-by: Lyude Paul <lyude@redhat.com>
>>>> Signed-off-by: Boqun Feng <boqun@kernel.org>
>>>> Link: https://patch.msgid.link/20260121223933.1568682-3-lyude@redhat.com
>>>> ---
>>>> include/linux/hardirq.h | 16 ++++++++++++----
>>>> include/linux/preempt.h | 13 +++++++++----
>>>> kernel/softirq.c        |  2 ++
>>>> 3 files changed, 23 insertions(+), 8 deletions(-)
>>>> 
>>>> diff --git a/include/linux/hardirq.h b/include/linux/hardirq.h
>>>> index d57cab4d4c06..cc06bda52c3e 100644
>>>> --- a/include/linux/hardirq.h
>>>> +++ b/include/linux/hardirq.h
>>>> @@ -10,6 +10,8 @@
>>>> #include <linux/vtime.h>
>>>> #include <asm/hardirq.h>
>>>> 
>>>> +DECLARE_PER_CPU(unsigned int, nmi_nesting);
>>>> +
>>>> extern void synchronize_irq(unsigned int irq);
>>>> extern bool synchronize_hardirq(unsigned int irq);
>>>> 
>>>> @@ -102,14 +104,16 @@ void irq_exit_rcu(void);
>>>>  */
>>>> 
>>>> /*
>>>> - * nmi_enter() can nest up to 15 times; see NMI_BITS.
>>>> + * nmi_enter() can nest - nesting is tracked in a per-CPU counter.
>>>>  */
>>>> #define __nmi_enter()                        \
>>>>    do {                            \
>>>>        lockdep_off();                    \
>>>>        arch_nmi_enter();                \
>>>> -        BUG_ON(in_nmi() == NMI_MASK);            \
>>>> -        __preempt_count_add(NMI_OFFSET + HARDIRQ_OFFSET);    \
>>>> +        BUG_ON(__this_cpu_read(nmi_nesting) == UINT_MAX);    \
>>> 
>>> I think we should keep the max nesting fixed to 15. If this doesn't trigger
>>> until UINT_MAX, it may take a long time to see that, and there's no reason
>>> NMIs should nest more than 15 anyway.
> 
> 
> 
>>> 
>>> Just because the counter allows it, doesn't me the system should allow it.
>> 
>> That's fine with me. Boqun, do you want to make the one-line change to the patch?
>> 
> 
> Something like this on top of your patch?
> 
> diff --git a/include/linux/hardirq.h b/include/linux/hardirq.h
> index cc06bda52c3e..a59a33e0f5ca 100644
> --- a/include/linux/hardirq.h
> +++ b/include/linux/hardirq.h
> @@ -110,7 +110,8 @@ void irq_exit_rcu(void);
>    do {                            \
>        lockdep_off();                    \
>        arch_nmi_enter();                \
> -        BUG_ON(__this_cpu_read(nmi_nesting) == UINT_MAX);    \
> +        /* Maximum NMI nesting is 15 */            \
> +        BUG_ON(__this_cpu_read(nmi_nesting) == 15);    \
>        __this_cpu_inc(nmi_nesting);            \
>        __preempt_count_add(HARDIRQ_OFFSET);        \
>        preempt_count_set(preempt_count() | NMI_MASK);    \
> 
> I will need to adjust this in patch #10 as well, but shouldn't be hard.

Maybe >= but this sounds good to me. Thanks for adjusting the patches.

Thanks!



> 
> Regards,
> Boqun
> 
>> Thanks.
>> 

  reply	other threads:[~2026-05-12 23:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-08  4:21 [PATCH 00/11] Refcounted interrupt disable and SpinLockIrq for rust (Part 1) Boqun Feng
2026-05-08  4:21 ` [PATCH 01/11] preempt: Introduce HARDIRQ_DISABLE_BITS Boqun Feng
2026-05-12 16:28   ` Steven Rostedt
2026-05-08  4:21 ` [PATCH 02/11] preempt: Track NMI nesting to separate per-CPU counter Boqun Feng
2026-05-12 16:30   ` Steven Rostedt
2026-05-12 19:22     ` Joel Fernandes
2026-05-12 22:16       ` Boqun Feng
2026-05-12 23:33         ` Joel Fernandes [this message]
2026-05-08  4:21 ` [PATCH 03/11] preempt: Introduce __preempt_count_{sub, add}_return() Boqun Feng
2026-05-09 18:09   ` Heiko Carstens
2026-05-08  4:21 ` [PATCH 04/11] openrisc: Include <linux/cpumask.h> in smp.h Boqun Feng
2026-05-08  4:21 ` [PATCH 05/11] irq & spin_lock: Add counted interrupt disabling/enabling Boqun Feng
2026-05-08  4:21 ` [PATCH 06/11] irq: Add KUnit test for refcounted interrupt enable/disable Boqun Feng
2026-05-08  4:21 ` [PATCH 07/11] locking: Switch to _irq_{disable,enable}() variants in cleanup guards Boqun Feng
2026-05-08  4:21 ` [PATCH 08/11] sched: Remove the unused preempt_offset parameter of __cant_sleep() Boqun Feng
2026-05-08  4:21 ` [PATCH 09/11] sched: Avoid signed comparison of preempt_count() in __cant_migrate() Boqun Feng
2026-05-08  4:21 ` [PATCH 10/11] preempt: Introduce PREEMPT_COUNT_64BIT Boqun Feng
2026-05-08  4:21 ` [PATCH 11/11] arm64: sched/preempt: Enable PREEMPT_COUNT_64BIT Boqun Feng
2026-05-08  8:22   ` Mark Rutland
2026-05-08 14:48     ` Boqun Feng
2026-05-09 18:12 ` [PATCH 00/11] Refcounted interrupt disable and SpinLockIrq for rust (Part 1) Heiko Carstens
2026-05-09 18:21   ` Boqun Feng

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=AEF2F57C-4120-4F2E-9063-EF314F787104@nvidia.com \
    --to=joelagnelf@nvidia.com \
    --cc=a.hindborg@kernel.org \
    --cc=ada.coupriediaz@arm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=aliceryhl@google.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=bigeasy@linutronix.de \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=boqun@kernel.org \
    --cc=borntraeger@linux.ibm.com \
    --cc=bp@alien8.de \
    --cc=bsegall@google.com \
    --cc=catalin.marinas@arm.com \
    --cc=dakr@kernel.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=gary@garyguo.net \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=hpa@zytor.com \
    --cc=joelaf@google.com \
    --cc=jonas@southpole.se \
    --cc=juri.lelli@redhat.com \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-openrisc@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=lossin@kernel.org \
    --cc=lyude@redhat.com \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=nikunj@amd.com \
    --cc=ojeda@kernel.org \
    --cc=pawan.kumar.gupta@linux.intel.com \
    --cc=peterz@infradead.org \
    --cc=rdunlap@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=ruanjinjie@huawei.com \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=seanjc@google.com \
    --cc=shorne@gmail.com \
    --cc=sohil.mehta@intel.com \
    --cc=stefan.kristiansson@saunalahti.fi \
    --cc=svens@linux.ibm.com \
    --cc=tglx@kernel.org \
    --cc=tmgross@umich.edu \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.com \
    --cc=will@kernel.org \
    --cc=x86@kernel.org \
    --cc=xin@zytor.com \
    --cc=ynorov@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox