From: Daniel Wagner <wagi@monom.org>
To: Steven Rostedt <rostedt@goodmis.org>, Carsten Emde <C.Emde@osadl.org>
Cc: Daniel Wagner <daniel.wagner@bmw-carit.de>,
linux-rt-users@vger.kernel.org, Jon Masters <jcm@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-kernel@vger.kernel.org,
Tom Zanussi <tom.zanussi@linux.intel.com>
Subject: Re: [PATCH] hwlat_detector: Detect hardware-induced latencies
Date: Mon, 13 Apr 2015 10:31:30 +0200 [thread overview]
Message-ID: <552B7EE2.1090005@monom.org> (raw)
In-Reply-To: <20150409101037.4dd0837a@gandalf.local.home>
Hi,
On 04/09/2015 04:10 PM, Steven Rostedt wrote:
> On Thu, 09 Apr 2015 15:46:12 +0200
> Carsten Emde <C.Emde@osadl.org> wrote:
>
>> Hi Daniel,
>>
>>> BTW, are you also taking care of the latency-hist.patch patch?
>> I do.
>>
>> However, the request (and the challenge) is not to simply rewrite the
>> code. The idea is to provide a general histogram framework that can be
>> used from anywhere in the kernel and to equip it with everything needed
>> by the existing histograms. This framework should no longer be part of
>> the RT patches but submitted directly to mainline Linux. In a second
>> step, we will then rewrite the existing histogram code to use the new
>> framework.
>>
>> Any help is greatly appreciated!
I'll start poking around then :)
> Hmm, Currently Tom Zanussi is working on a hist trigger for tracing.
> Not sure it can be used here, but perhaps ideas can be spawned.
>
> http://marc.info/?l=linux-kernel&m=142807630917288
>From a quick look, it should be possible to add on top of those patches
the two TRACE_EVENTs (preemptirqsoff_hist, hrtimer_interrupt), annotate
start_critical_*() & and friends (from latency-hist.patch). I'll try
that and see what explodes.
cheers,
daniel
prev parent reply other threads:[~2015-04-13 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 15:47 [PATCH] hwlat_detector: Detect hardware-induced latencies Daniel Wagner
2015-04-08 16:35 ` Steven Rostedt
2015-04-09 9:25 ` Daniel Wagner
2015-04-09 13:46 ` Carsten Emde
2015-04-09 14:10 ` Steven Rostedt
2015-04-13 8:31 ` 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=552B7EE2.1090005@monom.org \
--to=wagi@monom.org \
--cc=C.Emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=daniel.wagner@bmw-carit.de \
--cc=jcm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).