[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180830205509.51a2ed34@vmware.local.home>
Date: Thu, 30 Aug 2018 20:55:09 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc: linux-kernel@...r.kernel.org, mingo@...nel.org,
jiangshanlai@...il.com, dipankar@...ibm.com,
akpm@...ux-foundation.org, mathieu.desnoyers@...icios.com,
josh@...htriplett.org, tglx@...utronix.de, peterz@...radead.org,
dhowells@...hat.com, edumazet@...gle.com, fweisbec@...il.com,
oleg@...hat.com, joel@...lfernandes.org, Tejun Heo <tj@...nel.org>
Subject: Re: [PATCH tip/core/rcu 3/3] srcu: Make early-boot call_srcu()
reuse workqueue lists
On Thu, 30 Aug 2018 17:09:52 -0700
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> wrote:
> On Thu, Aug 30, 2018 at 07:53:22PM -0400, Steven Rostedt wrote:
> > On Thu, 30 Aug 2018 16:12:11 -0700
> > "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> wrote:
> >
> >
> > > > > - WARN_ON_ONCE(rcu_scheduler_active == RCU_SCHEDULER_INIT);
> > > >
> > > > Well it boots without warning ;-)
> > > >
> > > > Tested-by: Steven Rostedt (VMware) <rostedt@...dmis.org>
> > >
> > > Thank you again! I applied this to 1/3 and 3/3 on the assumption that
> > > you did not run rcutorture. ;-)
> >
> > No rcutorture. Just reverted the tracepoint SRCU delay patch and it
> > boots with the trace event enabled.
>
> Very good, then I did get it right. 1/3 and 3/3, but not 2/3.
>
I did apply 2, but didn't enable rcutorture. I just applied the entire
series.
-- Steve
Powered by blists - more mailing lists