[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180810123246.1174ba66@gandalf.local.home>
Date: Fri, 10 Aug 2018 12:32:46 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Joel Fernandes <joel@...lfernandes.org>
Cc: linux-kernel@...r.kernel.org, kernel-team@...roid.com,
Boqun Feng <boqun.feng@...il.com>,
Byungchul Park <byungchul.park@....com>,
Ingo Molnar <mingo@...hat.com>,
Masami Hiramatsu <mhiramat@...nel.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Namhyung Kim <namhyung@...nel.org>,
Paul McKenney <paulmck@...ux.vnet.ibm.com>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Glexiner <tglx@...utronix.de>,
Tom Zanussi <tom.zanussi@...ux.intel.com>
Subject: Re: [PATCH v12 2/3] tracepoint: Make rcuidle tracepoint callers use
SRCU
On Fri, 10 Aug 2018 11:35:54 -0400
Steven Rostedt <rostedt@...dmis.org> wrote:
> Investigating it, it's that when we register more than one event, the
> tracepoint code calls "release_probes" when adding new tracepoints (as
> it updated the tracepoint array), and this is done very early in boot
> up, causing this warning.
>
> I'm still looking at ways to fix this. Any ideas would help.
I just posted a patch:
http://lkml.kernel.org/r/20180810123042.51ceddb9@gandalf.local.home
It appears to fix the issue. I'm going to start testing it in my suite.
Does anyone have any concerns about it, or a better solution?
Thanks!
-- Steve
Powered by blists - more mailing lists