linux-kernel - Re: Multiple Tracers

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: <49DD6791.2010507@cn.fujitsu.com>
Date:	Thu, 09 Apr 2009 11:12:17 +0800
From:	Li Zefan <lizf@...fujitsu.com>
To:	Arnaldo Carvalho de Melo <acme@...hat.com>
CC:	Ingo Molnar <mingo@...e.hu>,
	Steven Whitehouse <swhiteho@...hat.com>,
	Tom Zanussi <tzanussi@...il.com>,
	Frédéric Weisbecker <fweisbec@...il.com>,
	rostedt@...dmis.org, linux-kernel@...r.kernel.org,
	mingo@...hat.com, axboe@...nel.dk
Subject: Re: Multiple Tracers

>>> Tom Zanussi (Cc:-ed) recently converted the blktrace tracepoints to 
>> I guess you mean Arnaldo <acme@...hat.com> ;)
> 
> Nope, Tom:
> 
> Message-Id: <1235725261.8512.89.camel@...rm-linux>
>  

Ah, sorry for the mistake, I didn't notice that patch, and I thought
Ingo meant the ftrace-plugin patch.

>>> a tracing framework - and i think much of that could be reused to 
>>> add EVENT_TRACE() tracepoints to blktrace too.
>>>
>>> Tom, what's your take on this?
>>>
>>> In general, this is the direction we want to take: EVENT_TRACE() 
>>> tracepoints that can be used in a generic way, in any tracer.
>>>
>> Actually we've planed to do this, and for other tracers.
> 
> Yeah, being able to mix all kinds of tracers is the way to go.
> 
--
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/