[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221020145340.5feef48f@gandalf.local.home>
Date: Thu, 20 Oct 2022 14:53:40 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: "Paul E. McKenney" <paulmck@...nel.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@...r.kernel.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Joel Fernandes <joel@...lfernandes.org>,
Tom Zanussi <zanussi@...nel.org>
Subject: Re: [PATCH] tracing: Add trace_trigger kernel command line option
On Thu, 20 Oct 2022 10:55:12 -0700
"Paul E. McKenney" <paulmck@...nel.org> wrote:
> > synchronize_rcu() {
> > rcu_poll_gp_seq_start_unlocked() {
> > struct rcu_node *rnp = rcu_get_root();
> >
> > if (rcu_init_invoked()) {
> > lockdep_assert_irqs_enabled();
> > raw_spin_lock_irq_rcu_node(rnp);
> > }
> > rcu_poll_gp_seq_start(snap);
> > if (rcu_init_invoked())
> > raw_spin_unlock_irq_rcu_node(rnp); <<-- Interrupts enabled here
> > }
>
> Thank you for digging into this!
>
> Does the following help?
It does indeed!
I can remove the early_boot_irqs_disabled checks if you can add this to
this rc cycle and mark it stable.
-- Steve
Powered by blists - more mailing lists