mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Wagner <daniel.wagner@bmw-carit.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@redhat.com>,
	Tom Zanussi <tom.zanussi@linux.intel.com>,
	Carsten Emde <C.Emde@osadl.org>,
	linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	Daniel Wagner <daniel.wagner@bmw-carit.de>
Subject: [RFD 0/5] Add latency histogram
Date: Thu, 30 Apr 2015 12:06:20 +0200	[thread overview]
Message-ID: <1430388385-29558-1-git-send-email-daniel.wagner@bmw-carit.de> (raw)

Hi,

I would like to discuss a possible way of getting the feature of the
latecy_hist.patch [1] added to mainline.

"Latency histograms are primarily relevant in the context of real-time
enabled kernels (CONFIG_PREEMPT/CONFIG_PREEMPT_RT)and are used in the
quality management of the Linux real-time capabilities."

Steven pointed out that this might be doable based on Tom Zanussi's
"[PATCH v4 0/7] tracing: 'hist' triggers" [2].

Here are my findings. It was not too complicated to get it working,
though I had to add some hacks. I have added comments to each patch.

cheers,
daniel

[2] https://lkml.org/lkml/2015/4/10/591
[1] https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit/?h=v3.14-rt-rebase&id=56d50cc34943bbba12b8c5942ee1ae3b29f73acb

Daniel Wagner (4):
  tracing: Add support to sort on the key
  tracing: Add option to quantize key values
  tracing: Deference pointers without RCU checks
  tracing: Add trace_irqsoff tracepoints

Tom Zanussi (1):
  tracing: 'hist' triggers

 include/linux/rculist.h             | 36 +++++++++++++++++++++++++++++
 include/linux/tracepoint.h          |  4 ++--
 include/trace/events/latency.h      | 40 ++++++++++++++++++++++++++++++++
 kernel/trace/trace_events_hist.c    | 46 +++++++++++++++++++++++++++++++++----
 kernel/trace/trace_events_trigger.c | 18 +++++++++------
 kernel/trace/trace_irqsoff.c        | 38 ++++++++++++++++++++++++++++++
 6 files changed, 168 insertions(+), 14 deletions(-)
 create mode 100644 include/trace/events/latency.h

-- 
2.1.0


             reply	other threads:[~2015-04-30 10:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30 10:06 Daniel Wagner [this message]
2015-04-30 10:06 ` [RFD 1/5] tracing: 'hist' triggers Daniel Wagner
2015-04-30 10:06 ` [RFD 2/5] tracing: Add support to sort on the key Daniel Wagner
2015-05-01  2:02   ` Tom Zanussi
2015-04-30 10:06 ` [RFD 3/5] tracing: Add option to quantize key values Daniel Wagner
2015-05-01  2:12   ` Tom Zanussi
2015-04-30 10:06 ` [RFD 4/5] tracing: Deference pointers without RCU checks Daniel Wagner
2015-04-30 10:06 ` [RFD 5/5] tracing: Add trace_irqsoff tracepoints Daniel Wagner
2015-05-01  2:14   ` Tom Zanussi
2015-05-01  2:54     ` Steven Rostedt
2015-05-01  9:23       ` Daniel Wagner
2015-05-04 14:05         ` Daniel Wagner
2015-05-04 15:41           ` Daniel Wagner
2015-05-06  6:31   ` Daniel Wagner
2015-05-01  1:52 ` [RFD 0/5] Add latency histogram Tom Zanussi
2015-05-01  9:22   ` Daniel Wagner

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=1430388385-29558-1-git-send-email-daniel.wagner@bmw-carit.de \
    --to=daniel.wagner@bmw-carit.de \
    --cc=C.Emde@osadl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=tom.zanussi@linux.intel.com \
    /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

all inboxes | Powered by JetHome®