From: Joel Fernandes <joelaf@google.com>
To: linux-kernel@vger.kernel.org
Cc: Joel Fernandes <joelaf@google.com>,
Steven Rostedt <rostedt@goodmis.org>,
kernel-team@android.com
Subject: [PATCH 0/2] tracing: Add critical section event support
Date: Sun, 3 Sep 2017 01:50:49 -0700 [thread overview]
Message-ID: <20170903085051.6348-1-joelaf@google.com> (raw)
These patches add critical section event tracing support.
Changes since RFC [1] are:
- Make critical events independent of the preempt/irqsoff tracer.
- Store pointers instead of symbol names to do less in the fast path.
- Other changes based on Steven's comments.
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
[1] https://patchwork.kernel.org/patch/9676579/
Joel Fernandes (2):
tracing: irqsoff: Move code under tracer config options
tracing: Add support for critical section events
include/linux/ftrace.h | 2 +-
include/linux/irqflags.h | 3 +-
include/trace/events/critical.h | 45 ++++++
kernel/trace/Kconfig | 5 +
kernel/trace/Makefile | 1 +
kernel/trace/trace_irqsoff.c | 331 ++++++++++++++++++++++++++--------------
6 files changed, 269 insertions(+), 118 deletions(-)
create mode 100644 include/trace/events/critical.h
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: kernel-team@android.com
--
2.14.1.581.gf28d330327-goog
next reply other threads:[~2017-09-03 8:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-03 8:50 Joel Fernandes [this message]
2017-09-03 8:50 ` [PATCH 1/2] tracing: irqsoff: Move code under tracer config options Joel Fernandes
2017-09-03 8:50 ` [PATCH 2/2] tracing: Add support for critical section events Joel Fernandes
2017-09-04 7:56 ` Peter Zijlstra
2017-09-04 19:04 ` Joel Fernandes
2017-09-04 19:44 ` Peter Zijlstra
2017-09-04 23:34 ` Steven Rostedt
2017-09-05 0:54 ` Joel Fernandes
2017-09-05 3:26 ` Joel Fernandes
2017-09-05 6:52 ` Peter Zijlstra
2017-09-05 16:35 ` Joel Fernandes
2017-09-06 8:40 ` Peter Zijlstra
2017-09-07 0:22 ` Joel Fernandes
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=20170903085051.6348-1-joelaf@google.com \
--to=joelaf@google.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).