linux-kernel - Re: [Patch] Tracing/ftrace: Adds a marker to allow user comments

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:	Sat, 6 Sep 2008 13:39:55 +0200
From:	"Frédéric Weisbecker" <fweisbec@...il.com>
To:	"Steven Rostedt" <rostedt@...dmis.org>
Cc:	"Pekka Paalanen" <pq@....fi>, "Ingo Molnar" <mingo@...e.hu>,
	"Linux Kernel" <linux-kernel@...r.kernel.org>
Subject: Re: [Patch] Tracing/ftrace: Adds a marker to allow user comments

2008/9/4 Steven Rostedt <rostedt@...dmis.org>:

> For logdev (my pet project from way back, and the latest ftrace is based
> on), I had a CUSTOM type. The API allowed to register a callback to a
> type, and it would associate that type to some number (descriptor) and
> pass that number back to you. Then you could use this number to write to
> the buffer using the CUSTOM type and registered number. On output, when a
> CUSTOM type is detected, it would read the custom.id (the number) and
> search for any registered callbacks to handle the entry.
>
> This probably would not be too difficult to implement. Especially since it
> is already implemented in logdev.
> (see http://rostedt.homelinux.com/logdev/)
>
> -- Steve

Why not. It is a way for a tracer to handle output for any type of entries.
But will this feature really be used for other special types than
TRACE_PRINT? I'm not sure... If it is not the case, the Pekka's
solution seems to me far more simple.

But actually I don't know the needs of others tracers...
--
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/