linux-kernel - Re: [PATCH] hwlat_detector: Detect hardware-induced latencies

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]

Date:	Thu, 9 Apr 2015 10:10:37 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Carsten Emde <C.Emde@...dl.org>
Cc:	Daniel Wagner <daniel.wagner@...-carit.de>,
	linux-rt-users@...r.kernel.org, Jon Masters <jcm@...hat.com>,
	Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
	linux-kernel@...r.kernel.org,
	Tom Zanussi <tom.zanussi@...ux.intel.com>
Subject: Re: [PATCH] hwlat_detector: Detect hardware-induced latencies

On Thu, 09 Apr 2015 15:46:12 +0200
Carsten Emde <C.Emde@...dl.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!

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

-- Steve
--
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/