linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>,
	Binoy Jayan <binoy.jayan@linaro.org>
Subject: [PATCH v5 0/4] *** Latency histograms - IRQSOFF,PREEMPTOFF ***
Date: Fri,  2 Sep 2016 18:07:27 +0530	[thread overview]
Message-ID: <1472819851-12857-1-git-send-email-binoy.jayan@linaro.org> (raw)

Hi,

Thank you Daniel, Steven for reviewing the code and for the comments.
I have made the changes mentioned below and have added the hack to mark
the field cpu as a key.

These set of patches [v5] capture latency events caused by interrupts and
premption disabled in kernel. The patches are based on the hist trigger
feature developed by Tom Zanussi.

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

Changes from v4
  - Added unlikely() for less probable paths
  - Dropped field 'ccomm' for hrtimer latency
  - Patch to mark the generic field cpu as a key field and make it part
    of histogram output
  - Changed ambiguous function names

TODO:
1. kselftest test scripts
2. delayed hrtimer offset test scenario

Thanks,
Binoy

Binoy Jayan (3):
  tracing: Add cpu as a key field in histogram
  tracing: Add trace_irqsoff tracepoints
  tracing: Histogram for delayed hrtimer offsets

Daniel Wagner (1):
  tracing: Deference pointers without RCU checks

 include/linux/hrtimer.h             |  3 ++
 include/linux/rculist.h             | 36 ++++++++++++++++++
 include/linux/tracepoint.h          |  4 +-
 include/trace/events/latency.h      | 73 +++++++++++++++++++++++++++++++++++++
 kernel/time/hrtimer.c               | 46 +++++++++++++++++++++++
 kernel/trace/trace_events.c         |  3 +-
 kernel/trace/trace_events_filter.c  |  4 +-
 kernel/trace/trace_events_hist.c    | 15 ++++++++
 kernel/trace/trace_events_trigger.c |  6 +--
 kernel/trace/trace_irqsoff.c        | 35 ++++++++++++++++++
 10 files changed, 217 insertions(+), 8 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

             reply	other threads:[~2016-09-02 12:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-02 12:37 Binoy Jayan [this message]
2016-09-02 12:37 ` [PATCH v5 1/4] tracing: Deference pointers without RCU checks Binoy Jayan
2016-09-02 12:37 ` [PATCH v5 2/4] tracing: Add cpu as a key field in histogram Binoy Jayan
2016-09-02 13:09   ` Steven Rostedt
2016-09-05  5:40   ` Daniel Wagner
2016-09-02 12:37 ` [PATCH v5 3/4] tracing: Add trace_irqsoff tracepoints Binoy Jayan
2016-09-02 13:14   ` Steven Rostedt
2016-09-02 12:37 ` [PATCH v5 4/4] tracing: Histogram for delayed hrtimer offsets Binoy Jayan
2016-09-02 13:20   ` Steven Rostedt

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=1472819851-12857-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 \
    /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).