linux-kernel - Re: [RFD 5/5] tracing: Add trace

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]

Date:	Fri, 01 May 2015 09:23:48 +0000
From:	Daniel Wagner <wagi@...om.org>
To:	Steven Rostedt <rostedt@...dmis.org>,
	Tom Zanussi <tom.zanussi@...ux.intel.com>
CC:	Daniel Wagner <daniel.wagner@...-carit.de>,
	Ingo Molnar <mingo@...hat.com>,
	Carsten Emde <C.Emde@...dl.org>,
	linux-rt-users@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFD 5/5] tracing: Add trace_irqsoff tracepoints

On 05/01/2015 02:54 AM, Steven Rostedt wrote:
> On Thu, 30 Apr 2015 21:14:52 -0500
> Tom Zanussi <tom.zanussi@...ux.intel.com> wrote:
>
>
>>> 'hist:key=latency.bucket:val=hitcount:sort=latency if cpu==0'
>>>
>>> but I haven't got this working. I didn't spend much time figuring out
>>> why this doesn't work. Even if the above is working you still
>>
>> I think it doesn't work because the tracepoint doesn't actually have a
>> 'cpu' field to use in the filter...
>
> Perhaps we should add special fields that don't use the tracepoint
> field, but can use generically know fields that are always known when
> the tracepoint is triggered. COMM could be one, as well as CPU.

I'll give it a try if no one objects next week (public holiday today :))

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/