mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Tom Zanussi <tzanussi@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE][PATCH 0 of 4] zedtrace, a general-purpose binary tracer
Date: Sat, 28 Feb 2009 16:00:31 -0500	[thread overview]
Message-ID: <20090228210031.GA8155@infradead.org> (raw)
In-Reply-To: <1235725238.8512.86.camel@charm-linux>

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.


  parent reply	other threads:[~2009-02-28 21:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-27  9:00 Tom Zanussi
2009-02-27 16:46 ` Frederic Weisbecker
2009-02-28  4:33   ` Tom Zanussi
2009-02-28 21:00 ` Christoph Hellwig [this message]
2009-03-02 15:41   ` Steven Rostedt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090228210031.GA8155@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tzanussi@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome