linux-kernel - Re: [RFC][PATCH 0/3] tracing: Add Hardware Latency detector tracer

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160809143036.72f9f67b@gandalf.local.home>
Date:	Tue, 9 Aug 2016 14:30:36 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Clark Williams <williams@...hat.com>
Cc:	Carsten Emde <C.Emde@...dl.org>, linux-kernel@...r.kernel.org,
	linux-rt-users@...r.kernel.org, Ingo Molnar <mingo@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Jon Masters <jcm@...hat.com>, Daniel Wagner <wagi@...om.org>,
	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Subject: Re: [RFC][PATCH 0/3] tracing: Add Hardware Latency detector tracer

On Tue, 9 Aug 2016 13:15:16 -0500
Clark Williams <williams@...hat.com> wrote:

> On Thu, 4 Aug 2016 11:30:33 -0400
> Steven Rostedt <rostedt@...dmis.org> wrote:
> 
> > Note, I'm currently working on adding code to detect NMIs to this as
> > well. And perhaps even tracing SMI counters. Just to show what caused
> > the latency, as latency isn't measured by the counters (that I know of).
> >   
> 
> I like the trace report, but for one small thing; I think it's worth
> either adding units to the reported latency values (us suffix) or
> putting in a header line that hwlatdetect values are reported in
> microseconds.

Yeah, adding "us" to the time stamps would be useful. I'll update.

-- Steve