LKML Archive on
help / color / mirror / Atom feed
From: Andrew Morton <>
To: "David J. Wilder" <>
Subject: Re: [PATCH 0/3] A kernel tracing interface
Date: Thu, 28 Feb 2008 02:04:37 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, 26 Feb 2008 14:38:37 -0800 "David J. Wilder" <> wrote:

> These patches provide a kernel tracing interface called "trace".
> ChangeLog:
> -Updated to 2.6.25-rc2-mm1
> -Removed sem_watch example, to hard to maintain.
> -Added a new example that demonstrates per-cpu continuous tracing
>  of data generated using marker probes.
> -Removed inline from relay patch.
> -Moved examples into /sample directory.
> The motivation for "trace" is to:
> - Provide a simple set of tracing primitives that will utilize the high-
>   performance and low-overhead of relayfs for passing traces data from
>   kernel to user space.
> - Provide a common user interface for managing kernel traces.
> - Allow for binary as well as ascii trace data.
> - Incorporate features from the systemtap runtime that are
>   useful to others.

So... what's the story on this versus lttng?

Is there some userspace code available for people to test this?  Maybe it's
mentioned and I missed it.

It'd be interesting to see a writeup of the proposed kernel<->userspace
interfaces.  I see a description of kernel-internal interfaces, but how do
users use it?

I see it uses things from blktrace.  Can blktrace be switched over to being
a client of this code?

  reply	other threads:[~2008-02-28 10:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26 22:38 [PATCH 0/3] A kernel tracing interface David J. Wilder
2008-02-28 10:04 ` Andrew Morton [this message]
2008-02-28 19:40   ` David Wilder
2008-02-29  5:36     ` K. Prasad
2008-02-29 12:08       ` K. Prasad
  -- strict thread matches above, loose matches on Subject: below --
2007-11-13  1:02 David J. Wilder
2007-10-02 18:55 David J. Wilder
2007-10-02 16:33 David J. Wilder

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:

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

  git send-email \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).