lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5526458E.5050202@bmw-carit.de>
Date:	Thu, 9 Apr 2015 11:25:34 +0200
From:	Daniel Wagner <daniel.wagner@...-carit.de>
To:	Steven Rostedt <rostedt@...dmis.org>
CC:	<linux-rt-users@...r.kernel.org>, Jon Masters <jcm@...hat.com>,
	Carsten Emde <C.Emde@...dl.org>,
	Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] hwlat_detector: Detect hardware-induced latencies

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ