Re: [ANNOUNCE][PATCH 0 of 4] zedtrace, a general-purpose binarytracer

[Christoph Hellwig]

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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/