public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joel Fernandes <joelaf@google.com>
To: linux-kernel@vger.kernel.org
Cc: Joel Fernandes <joelaf@google.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Peter Zijlstra <peterz@infradead.org>,
	kernel-team@android.com
Subject: [PATCH RFC v4 0/3] tracing: Add trace events for preemption and irq disable/enable.
Date: Wed,  6 Sep 2017 17:17:49 -0700	[thread overview]
Message-ID: <20170907001752.27015-1-joelaf@google.com> (raw)

These patches add trace events support for preempt and irq disable/enable
events.

Changes since v3 (link [1]):
Previously the patch series used the terms "critical section" but Peter
suggested that this name is confusing due to ambiguity, so I dropped calling it
that in this series. See discussion in [1]. I also dropped the "preemptirq"
combined event (which behaves similar to the preemptirqsoff tracer) for now and
will keep that for a later patch once we can get this foundation series in.

Here's an example of how Android's systrace will be using it to show atomic
sections as a gantt chart: http://imgur.com/download/TZplEVp

I also added a slightly unrelated fix for a config option (patch 3/3).

[1] https://patchwork.kernel.org/patch/9936045/

Joel Fernandes (3):
  trace/irqsoff: Prepare to add preempt and irq trace events
  trace: Add support for preempt and irq enable/disable events
  ftrace: Use correct config option for preemption debug

 include/linux/ftrace.h            |   7 +-
 include/linux/irqflags.h          |   4 +-
 include/trace/events/preemptirq.h |  62 +++++++++++++
 kernel/trace/Kconfig              |   9 ++
 kernel/trace/Makefile             |   1 +
 kernel/trace/trace_irqsoff.c      | 178 +++++++++++++++++++++++++++++++-------
 6 files changed, 226 insertions(+), 35 deletions(-)
 create mode 100644 include/trace/events/preemptirq.h

Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: kernel-team@android.com
-- 
2.14.1.581.gf28d330327-goog

             reply	other threads:[~2017-09-07  0:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-07  0:17 Joel Fernandes [this message]
2017-09-07  0:17 ` [PATCH RFC v4 1/3] tracing/irqsoff: Prepare to add preempt and irq trace events Joel Fernandes
2017-09-10  9:06   ` Steven Rostedt
2017-09-10 22:21     ` Joel Fernandes
2017-09-07  0:17 ` [PATCH RFC v4 2/3] tracing: Add support for preempt and irq enable/disable events Joel Fernandes
2017-09-07  0:17 ` [PATCH RFC v4 3/3] ftrace: Use correct config option for preemption debug 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=20170907001752.27015-1-joelaf@google.com \
    --to=joelaf@google.com \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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