linux-kernel - Re: [ANNOUNCE][PATCH 0 of 4] zedtrace, a general-purpose binary 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20090228210031.GA8155@infradead.org>
Date:	Sat, 28 Feb 2009 16:00:31 -0500
From:	Christoph Hellwig <hch@...radead.org>
To:	Tom Zanussi <tzanussi@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [ANNOUNCE][PATCH 0 of 4] zedtrace, a general-purpose binary
	tracer

I played with it a bit and I really like the userspace with the
transport backend and a hakcy script language that many people know
for post-processing.

But looking at the kernel portions just shows again that the whole
tracepoint concept is utterly wrong.  We should not need the
zed_block.c/zed_sched.c/zed_workqueue.c but instead have those
tracing points directly annotated in the subsystems like using
markers, so that's it's self-contained and can be added by modules
without touching the rest of the kernel.

I know tracepoints are not your fault, but we really need to sort
that out for a nice tracing experience.

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