linux-kernel - Re: [PATCH 2/4] tracing: add event trace infrastructure

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: <84144f020902250224kd8475b8yd9fd9f3ece7155e@mail.gmail.com>
Date:	Wed, 25 Feb 2009 12:24:20 +0200
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Ingo Molnar <mingo@...e.hu>, Steven Rostedt <rostedt@...dmis.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Theodore Tso <tytso@....edu>,
	Arjan van de Ven <arjan@...radead.org>,
	Pekka Paalanen <pq@....fi>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Jason Baron <jbaron@...hat.com>,
	Martin Bligh <mbligh@...gle.com>,
	Mathieu Desnoyers <compudj@...stal.dyndns.org>,
	"Frank Ch. Eigler" <fche@...hat.com>,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	Jens Axboe <jens.axboe@...cle.com>,
	Masami Hiramatsu <mhiramat@...hat.com>,
	Steven Rostedt <srostedt@...hat.com>
Subject: Re: [PATCH 2/4] tracing: add event trace infrastructure

Hi Andrew,

On Wed, 25 Feb 2009 10:56:23 +0100 Ingo Molnar <mingo@...e.hu> wrote:
>> Since the concept of a kernel tracing facility being
>> self-sufficient and being easy to use is an integral and key
>> concept to ftrace, dont you see why people take your suggestions
>> as a dismissal of the ftrace concept?

On Wed, Feb 25, 2009 at 12:02 PM, Andrew Morton
<akpm@...ux-foundation.org> wrote:
> Nothing I've suggested in any way makes ftrace hard to use.
>
> If you guys had gone this way, you would not have screwed it up as much
> as you're suggesting.

I find it difficult to understand what is it exactly that you're
suggesting. AFAICT, the core of the argument is how much
post-processing should we do in the kernel. Now keeping all
post-processing out of the kernel will make (some) tracers less
user-friendly but we obviously don't want to do a full TeX in the
kernel either.

Maybe identifying the specific plug-ins you have problems with would
be useful? I only know some of the ftrace core and the kmemtrace
plug-in and I suspect the situation is similar for other plug-in
developers as well. So the problem here could be just that you're not
getting the message across to the right people.

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