From: Steven Rostedt <rostedt@goodmis.org>
To: Peter Zilstra <peterz@infradead.org>
Cc: Joel Fernandes <joelaf@google.com>,
linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: Re: [PATCH v6 0/2] tracing: Add trace events for preemption and irq disable/enable
Date: Thu, 21 Sep 2017 23:11:32 -0400 [thread overview]
Message-ID: <20170921231132.464a3236@vmware.local.home> (raw)
In-Reply-To: <20170922015024.16123-1-joelaf@google.com>
Peter,
Do you have any qualms with this patch set?
-- Steve
On Thu, 21 Sep 2017 18:50:22 -0700
Joel Fernandes <joelaf@google.com> wrote:
> These patches add trace events support for preempt and irq disable/enable
> events.
>
> Changes since v5:
> - Use trace_*_rcuidle variants (thanks Steve!)
>
> Here's an example of how Android's systrace will be using it to show critical
> sections as a gantt chart: http://imgur.com/download/TZplEVp
>
> Links to earlier series:
> v5: https://lkml.org/lkml/2017/9/12/507
> v4: https://lkml.org/lkml/2017/9/6/724
> v3: https://lkml.org/lkml/2017/9/3/15
>
> Joel Fernandes (2):
> tracing: Prepare to add preempt and irq trace events
> tracing: Add support for preempt and irq enable/disable events
>
> include/linux/ftrace.h | 3 +-
> include/linux/irqflags.h | 4 +-
> include/trace/events/preemptirq.h | 66 ++++++++++++++
> kernel/trace/Kconfig | 9 ++
> kernel/trace/Makefile | 1 +
> kernel/trace/trace_irqsoff.c | 176 +++++++++++++++++++++++++++++++-------
> 6 files changed, 226 insertions(+), 33 deletions(-)
> create mode 100644 include/trace/events/preemptirq.h
>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Peter Zilstra <peterz@infradead.org>
prev parent reply other threads:[~2017-09-22 3:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 1:50 Joel Fernandes
2017-09-22 1:50 ` [PATCH v6 1/2] tracing: Prepare to add preempt and irq trace events Joel Fernandes
2017-09-22 1:50 ` [PATCH v6 2/2] tracing: Add support for preempt and irq enable/disable events Joel Fernandes
2017-09-22 9:02 ` Peter Zijlstra
2017-09-22 18:28 ` Joel Fernandes
2017-09-25 8:34 ` Peter Zijlstra
2017-09-25 10:15 ` Steven Rostedt
2017-09-25 10:32 ` Peter Zijlstra
2017-09-25 10:52 ` Steven Rostedt
2017-09-25 22:57 ` Joel Fernandes
2017-09-26 2:47 ` Steven Rostedt
2017-09-29 2:15 ` Joel Fernandes
2017-09-26 0:23 ` Joel Fernandes
2017-09-30 9:08 ` Steven Rostedt
2017-10-02 19:23 ` Joel Fernandes
2017-10-02 19:33 ` Joel Fernandes
2017-10-02 19:37 ` Steven Rostedt
2017-10-02 21:31 ` Joel Fernandes
2017-09-22 3:11 ` Steven Rostedt [this message]
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=20170921231132.464a3236@vmware.local.home \
--to=rostedt@goodmis.org \
--cc=joelaf@google.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
/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
Powered by JetHome