public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vara Prasad <prasadav@us.ibm.com>
To: David Wilder <dwilder@us.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	SystemTAP <systemtap@sources.redhat.com>,
	Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Subject: Re: [PATCH 0/2] A kernel tracing interface
Date: Tue, 18 Sep 2007 09:53:03 -0700	[thread overview]
Message-ID: <46F0026F.7030102@us.ibm.com> (raw)
In-Reply-To: <46EFFF9D.6090609@us.ibm.com>

David Wilder wrote:

> Andrew Morton wrote:
>
>> On Thu, 13 Sep 2007 16:43:09 -0700
>> David Wilder <dwilder@us.ibm.com> wrote:
>>
>>> These patches provide a kernel tracing interface called "trace".
>>>
>>> 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.
>>>
>>> History- Versions of this code have been submitted for review under
>>> a couple of different names.  The original submission was called UTT,
>>> it was later re-submitted as GTSC.   Christoph Hellwig commented "The
>>> code looks fine ...but the name is just dumb".  Following Christoph's
>>> advice, I changed the name to simply "Trace".
>>>
>>> This patch addresses review comments made by Christoph Hellwig and 
>>> Mathieu
>>> Desnoyers.  Changes include the addition of a mutex and synchronization
>>> protecting trace state changes (using RCU) and the reduction of the
>>> number of exports.
>>>
>>> Patches are against 2.6.23-rc4-mm1
>>>
>>> Required patches:
>>> 1/2 Trace code and documentation
>>> 2/2 Relay reset consumed  (required for trace's "rewind" feature")
>>>
>>> Signed-off-by: David Wilder <dwilder@us.ibm.com>
>>
>>
>> Well the code looks neat and easy enough to merge.
>>
>> What exactly is the relationship between this and systemtap and 
>> kprobes and
>> all the other tracing things which people are doing?
>>
>>
> The key to the relationship is relay.  Systemtap, kprobes, blktrace 
> ,(and others) need the fast user-kernel data hose that relay provides. 
> Trace is a means to simplify and standardize the use of relay. 
> Systemtap adopted this code some time ago in its own runtime.  Moving 
> this code into the kernel will allow other tracers to take advantage 
> of the same trace primitives.

Andrew,

This is part of the effort by the SystemTap team to move pieces of the 
project that are generic to mainline.

bye,
Vara Prasad


  reply	other threads:[~2007-09-18 16:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-13 23:43 [PATCH 0/2] A kernel tracing interface David Wilder
2007-09-15  0:49 ` Andrew Morton
2007-09-18 16:41   ` David Wilder
2007-09-18 16:53     ` Vara Prasad [this message]
2007-09-18 17:13       ` Andrew Morton
2007-09-18 17:55         ` Mathieu Desnoyers
2007-09-18 19:54           ` David Wilder
2007-09-18 19:41         ` David 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:
  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=46F0026F.7030102@us.ibm.com \
    --to=prasadav@us.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=dwilder@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=systemtap@sources.redhat.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