[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180810090601.32de3915@gandalf.local.home>
Date: Fri, 10 Aug 2018 09:06:01 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Joel Fernandes <joelaf@...gle.com>
Cc: Masami Hiramatsu <mhiramat@...nel.org>,
"Joel Fernandes (Google)" <joel@...lfernandes.org>,
LKML <linux-kernel@...r.kernel.org>,
"Cc: Android Kernel" <kernel-team@...roid.com>,
Ingo Molnar <mingo@...hat.com>,
Paul McKenney <paulmck@...ux.vnet.ibm.com>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Namhyung Kim <namhyung@...nel.org>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH ftrace/core] tracing: irqsoff: Account for additional
preempt_disable
On Fri, 10 Aug 2018 06:01:34 -0700
Joel Fernandes <joelaf@...gle.com> wrote:
> > Even though, it should be verified or atleast commented on the function header.
>
> Ok. ftrace/core has been fixed since since so this patch is outdated
> and isn't needed any more, but I agree a separate patch doc comment
> would help make it clear about this fact. Both IRQ and preempt
> tracepoints work this way, they fire only within their critical
> section.
Note, I'm keeping the patch in the git history. As an artifact that can
be found easily when looking at this code for further enhancements.
Feel free to send a patch that adds comments to these callbacks.
-- Steve
Powered by blists - more mailing lists