public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Wagner <daniel.wagner@bmw-carit.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: <linux-rt-users@vger.kernel.org>, Jon Masters <jcm@redhat.com>,
	Carsten Emde <C.Emde@osadl.org>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] hwlat_detector: Detect hardware-induced latencies
Date: Thu, 9 Apr 2015 11:25:34 +0200	[thread overview]
Message-ID: <5526458E.5050202@bmw-carit.de> (raw)
In-Reply-To: <20150408123550.7dbd61b4@gandalf.local.home>

Hi Steven,

On 04/08/2015 06:35 PM, Steven Rostedt wrote:
> On Wed, 08 Apr 2015 12:28:34 -0400
>> Hi,
>>
>> Here is my attempt to rewritte hwlat_detector. Most of the code is a
>> new except the detection routine itself. With some luck I didn't break
>> it.  I hope I updated the documentation correctly and also added all
>> the credits.
>>
>> @Carsten, I haven't found your original post of the hwlatdetect.patch
>> patch. I assume you have written most of the documentation. I guess
>> should be also added as copyright holder.
>>
> 
> Funny you are working on this. I'm actually working on porting the
> hwlat_detector to ftrace as a tracer and removing it as a module. It
> will be similar to the irqsoff tracer, although it wont be doing
> "latency" tests. It will just report the output to the ring buffer as
> the other tracers do.

Good to know. So best thing is to let this patch rest :) If need help
(e.g. testing) just let me know.

BTW, are you also taking care of the latency-hist.patch patch?

cheers,
daniel

  reply	other threads:[~2015-04-09  9:25 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 [this message]
2015-04-09 13:46     ` Carsten Emde
2015-04-09 14:10       ` Steven Rostedt
2015-04-13  8:31         ` 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=5526458E.5050202@bmw-carit.de \
    --to=daniel.wagner@bmw-carit.de \
    --cc=C.Emde@osadl.org \
    --cc=bigeasy@linutronix.de \
    --cc=jcm@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --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