From: Joel Fernandes <joelaf@google.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Joel Fernandes <joel@joelfernandes.org>,
LKML <linux-kernel@vger.kernel.org>,
"Cc: Android Kernel" <kernel-team@android.com>,
Boqun Feng <boqun.feng@gmail.com>,
Byungchul Park <byungchul.park@lge.com>,
Ingo Molnar <mingo@redhat.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Namhyung Kim <namhyung@kernel.org>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Glexiner <tglx@linutronix.de>,
Tom Zanussi <tom.zanussi@linux.intel.com>
Subject: Re: [PATCH v12 3/3] tracing: Centralize preemptirq tracepoints and unify their usage
Date: Tue, 07 Aug 2018 10:48:05 -0400 [thread overview]
Message-ID: <C1CB990F-8232-4168-89A8-E8C13B660B0B@google.com> (raw)
In-Reply-To: <20180807103410.4fe203cb@gandalf.local.home>
On August 7, 2018 10:34:10 AM EDT, Steven Rostedt <rostedt@goodmis.org> wrote:
>On Tue, 07 Aug 2018 10:10:59 -0400
>Joel Fernandes <joelaf@google.com> wrote:
>
>> On August 7, 2018 9:49:54 AM EDT, Steven Rostedt
><rostedt@goodmis.org> wrote:
>> >On Tue, 7 Aug 2018 06:33:35 -0700
>> >Joel Fernandes <joelaf@google.com> wrote:
>> >
>> >> Thanks, also one more thing I noticed in your patch,
>> >> lockdep_hardirqs_off needs to be called before all other probes
>but
>> >> you're calling it after. This is why I registered it with INT_MAX:
>> >>
>> >> register_trace_prio_irq_disable(lockdep_hardirqs_off, NULL,
>INT_MAX);
>> >>
>> >> Without it you may get annotation warnings. Thanks,
>> >
>> >Interesting. I was following the old way where we called the tracing
>> >code before calling the lockdep code (all hard coded and not from
>> >trace events). Is this have something to do with calling the code
>from
>> >a tracepoint?
>> >
>> >Do you have an example that could trigger the warning?
>> >
>>
>> I remember the warnings but can't remember now how I triggered them.
>> I think I saw them with the irqsoff tracer or irq trace events
>> running, with lockdep turned on.
>
>I'll see if I can trigger it. I'll run this all through my tests.
Ok.
>> Also an irq disable probe that does a lockdep assert that irqs are
>> disabled could trigger it?
>>
>
>You mean if someone add a tracepoint callback to the irq disable
>tracepoint, and did a lockdep assert to make sure interrupts are
>disabled?
Yes that's what I meant.
Thanks,
- Joel
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2018-08-07 14:48 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 22:24 [PATCH v12 0/3] tracing: Centralize preemptirq tracepoints and unify their usage Joel Fernandes
2018-07-30 22:24 ` [PATCH v12 1/3] lockdep: use this_cpu_ptr instead of get_cpu_var stats Joel Fernandes
2018-07-30 22:24 ` [PATCH v12 2/3] tracepoint: Make rcuidle tracepoint callers use SRCU Joel Fernandes
2018-07-30 23:10 ` Steven Rostedt
2018-08-10 15:35 ` Steven Rostedt
2018-08-10 16:32 ` Steven Rostedt
2018-07-30 22:24 ` [PATCH v12 3/3] tracing: Centralize preemptirq tracepoints and unify their usage Joel Fernandes
2018-08-06 19:50 ` Steven Rostedt
2018-08-07 0:43 ` Joel Fernandes
2018-08-07 1:43 ` Steven Rostedt
2018-08-07 13:33 ` Joel Fernandes
2018-08-07 13:49 ` Steven Rostedt
2018-08-07 14:10 ` Joel Fernandes
2018-08-07 14:34 ` Steven Rostedt
2018-08-07 14:48 ` Joel Fernandes [this message]
2018-08-07 15:09 ` Steven Rostedt
2018-08-07 15:24 ` Joel Fernandes
2018-08-07 23:45 ` Steven Rostedt
2018-08-07 23:54 ` Joel Fernandes
2018-08-08 0:48 ` Steven Rostedt
2018-08-08 1:17 ` Joel Fernandes
2018-08-08 1:55 ` Steven Rostedt
2018-08-08 2:13 ` Joel Fernandes
2018-08-08 2:28 ` Steven Rostedt
2018-08-08 3:44 ` Joel Fernandes
2018-08-08 3:53 ` Joel Fernandes
2018-08-08 5:06 ` Joel Fernandes
2018-08-08 12:46 ` Steven Rostedt
2018-08-08 13:03 ` Paul E. McKenney
2018-08-08 13:07 ` Steven Rostedt
2018-08-08 14:33 ` Paul E. McKenney
2018-08-08 14:49 ` Steven Rostedt
2018-08-08 15:05 ` Paul E. McKenney
2018-08-08 15:23 ` Steven Rostedt
2018-08-08 16:02 ` Paul E. McKenney
2018-08-08 16:24 ` Steven Rostedt
2018-08-08 17:21 ` Paul E. McKenney
2018-08-08 13:00 ` Paul E. McKenney
2018-08-08 14:10 ` Joel Fernandes
2018-08-08 14:49 ` Paul E. McKenney
2018-08-08 19:24 ` Joel Fernandes
2018-08-08 20:18 ` Paul E. McKenney
2018-08-08 22:15 ` Joel Fernandes
2018-08-08 22:47 ` Paul E. McKenney
2018-08-09 12:18 ` joel
2018-08-08 14:27 ` Steven Rostedt
2018-08-08 14:42 ` Paul E. McKenney
2018-08-08 15:27 ` Steven Rostedt
2018-08-08 16:03 ` Paul E. McKenney
2018-08-02 14:55 ` [PATCH v12 0/3] " Masami Hiramatsu
2018-08-03 2:57 ` Joel Fernandes
2018-08-03 7:23 ` Masami Hiramatsu
2018-08-04 4:51 ` Joel Fernandes
2018-08-05 16:46 ` Joel Fernandes
2018-08-06 2:07 ` Masami Hiramatsu
2018-08-06 15:24 ` Joel Fernandes
2018-08-03 7:34 ` Masami Hiramatsu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C1CB990F-8232-4168-89A8-E8C13B660B0B@google.com \
--to=joelaf@google.com \
--cc=boqun.feng@gmail.com \
--cc=byungchul.park@lge.com \
--cc=joel@joelfernandes.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tom.zanussi@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).