From: Binoy Jayan <binoy.jayan@linaro.org>
To: "Steven Rostedt (Red Hat)" <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Daniel Wagner <daniel.wagner@bmw-carit.de>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org,
Masami <masami.hiramatsu@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Binoy Jayan <binoy.jayan@linaro.org>
Subject: [PATCH v6 0/4] *** Latency histograms - IRQSOFF,PREEMPTOFF, Delayed HRTIMERS ***
Date: Wed, 7 Sep 2016 16:43:51 +0530 [thread overview]
Message-ID: <1473246835-30075-1-git-send-email-binoy.jayan@linaro.org> (raw)
Hi,
Thank you Daniel, Steven for reviewing the code and for the comments.
These set of patches [v6] capture latency events caused by interrupts and
premption disabled in kernel. The patches are based on the hist trigger
feature developed by Tom Zanussi.
v5: https://lkml.org/lkml/2016/9/2/246
v4: https://lkml.org/lkml/2016/8/30/188
v3: https://lkml.org/lkml/2016/8/29/50
v2: https://lkml.org/lkml/2016/8/24/296
v4 -> v5:
- Add hist trigger support for generic fields
- hrtimer latency event moved to hrtimer event headers
- Cleanup
-Binoy
Binoy Jayan (2):
tracing: Add trace_irqsoff tracepoints
tracing: Histogram for delayed hrtimer offsets
Daniel Wagner (2):
tracing: Deference pointers without RCU checks
tracing: Add hist trigger support for generic fields
include/linux/hrtimer.h | 3 ++
include/linux/rculist.h | 36 ++++++++++++++++++++++++
include/linux/tracepoint.h | 4 +--
include/trace/events/latency.h | 56 +++++++++++++++++++++++++++++++++++++
include/trace/events/timer.h | 25 +++++++++++++++++
kernel/time/Kconfig | 7 +++++
kernel/time/hrtimer.c | 52 ++++++++++++++++++++++++++++++++++
kernel/trace/trace_events.c | 13 +++++----
kernel/trace/trace_events_filter.c | 4 +--
kernel/trace/trace_events_hist.c | 36 ++++++++++++++++++++----
kernel/trace/trace_events_trigger.c | 6 ++--
kernel/trace/trace_irqsoff.c | 35 +++++++++++++++++++++++
12 files changed, 258 insertions(+), 19 deletions(-)
create mode 100644 include/trace/events/latency.h
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next reply other threads:[~2016-09-07 11:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 11:13 Binoy Jayan [this message]
2016-09-07 11:13 ` [PATCH v6 1/4] tracing: Deference pointers without RCU checks Binoy Jayan
2016-09-08 6:46 ` Masami Hiramatsu
2016-09-07 11:13 ` [PATCH v6 2/4] tracing: Add hist trigger support for generic fields Binoy Jayan
2016-09-07 13:39 ` kbuild test robot
2016-09-07 11:13 ` [PATCH v6 3/4] tracing: Add trace_irqsoff tracepoints Binoy Jayan
2016-09-07 16:42 ` Thomas Gleixner
2016-09-08 5:20 ` Daniel Wagner
2016-09-08 6:31 ` Thomas Gleixner
2016-09-08 8:06 ` Thomas Gleixner
2016-09-12 13:50 ` Steven Rostedt
2016-09-14 6:52 ` Binoy Jayan
2016-09-14 9:42 ` Thomas Gleixner
2016-09-07 11:13 ` [PATCH v6 4/4] tracing: Histogram for delayed hrtimer offsets Binoy Jayan
2016-09-08 6:56 ` Masami Hiramatsu
2016-09-08 7:10 ` Thomas Gleixner
2016-09-08 9:39 ` Binoy Jayan
2016-09-09 13:30 ` Thomas Gleixner
2016-09-23 14:20 ` Carsten Emde
2016-09-09 17:10 ` Mark Brown
2016-09-10 6:10 ` Thomas Gleixner
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=1473246835-30075-1-git-send-email-binoy.jayan@linaro.org \
--to=binoy.jayan@linaro.org \
--cc=arnd@arndb.de \
--cc=daniel.wagner@bmw-carit.de \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu@linaro.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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).