[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87edv54316.fsf@jogness.linutronix.de>
Date: Tue, 18 Oct 2022 16:37:01 +0206
From: John Ogness <john.ogness@...utronix.de>
To: "Paul E. McKenney" <paulmck@...nel.org>, rcu@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, kernel-team@...com,
rostedt@...dmis.org, "Paul E. McKenney" <paulmck@...nel.org>,
Randy Dunlap <rdunlap@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Petr Mladek <pmladek@...e.com>
Subject: Re: [PATCH RFC v2 rcu 2/8] srcu: Create an srcu_read_lock_nmisafe()
and srcu_read_unlock_nmisafe()
Hi Paul,
Sorry for the late response here. I am now trying to actually use this
series.
On 2022-09-29, "Paul E. McKenney" <paulmck@...nel.org> wrote:
> diff --git a/kernel/rcu/Kconfig b/kernel/rcu/Kconfig
> index d471d22a5e21..f53ad63b2bc6 100644
> --- a/kernel/rcu/Kconfig
> +++ b/kernel/rcu/Kconfig
> @@ -72,6 +72,9 @@ config TREE_SRCU
> help
> This option selects the full-fledged version of SRCU.
>
You are missing a:
+config ARCH_HAS_NMI_SAFE_THIS_CPU_OPS
+ bool
+
Otherwise there is no CONFIG_ARCH_HAS_NMI_SAFE_THIS_CPU_OPS, so for
example CONFIG_NEED_SRCU_NMI_SAFE always ends up with y on X86.
> +config NEED_SRCU_NMI_SAFE
> + def_bool HAVE_NMI && !ARCH_HAS_NMI_SAFE_THIS_CPU_OPS && !TINY_SRCU
> +
John
Powered by blists - more mailing lists