public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Wagner <wagi@monom.org>
To: Tom Zanussi <tom.zanussi@linux.intel.com>,
	Daniel Wagner <daniel.wagner@bmw-carit.de>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Ingo Molnar <mingo@redhat.com>, Carsten Emde <C.Emde@osadl.org>,
	linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFD 0/5] Add latency histogram
Date: Fri, 01 May 2015 09:22:46 +0000	[thread overview]
Message-ID: <554345E6.7040005@monom.org> (raw)
In-Reply-To: <1430445124.17922.12.camel@picadillo>

Hi Tom,

On 05/01/2015 01:52 AM, Tom Zanussi wrote:
> Hi Daniel,
>
> On Thu, 2015-04-30 at 12:06 +0200, Daniel Wagner wrote:
>> 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.
>>
>
> It looks like you were able to do quite a bit here with not much code -
> nice!

Thanks :)

> Just FYI, I'll be working on a v5 of the hist triggers patchset that
> will incorporate the stuff from patch 1 (needs to be split into a
> separate patch for the triggers code already upstream, and one for hist
> triggers) and your comments from patch 2 (see comments in my reply to
> that patch), along with  a couple other unrelated changes...

Great to hear!

cheers,
daniel


      reply	other threads:[~2015-05-01  9:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30 10:06 [RFD 0/5] Add latency histogram Daniel Wagner
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 [this message]

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=554345E6.7040005@monom.org \
    --to=wagi@monom.org \
    --cc=C.Emde@osadl.org \
    --cc=daniel.wagner@bmw-carit.de \
    --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