public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Vara Prasad <prasadav@us.ibm.com>,
	David Wilder <dwilder@us.ibm.com>,
	linux-kernel@vger.kernel.org,
	SystemTAP <systemtap@sources.redhat.com>
Subject: Re: [PATCH 0/2] A kernel tracing interface
Date: Tue, 18 Sep 2007 13:55:22 -0400	[thread overview]
Message-ID: <20070918175521.GA2915@Krystal> (raw)
In-Reply-To: <20070918101327.91c5f24f.akpm@linux-foundation.org>

* Andrew Morton (akpm@linux-foundation.org) wrote:
> On Tue, 18 Sep 2007 09:53:03 -0700 Vara Prasad <prasadav@us.ibm.com> wrote:
> 
> > This is part of the effort by the SystemTap team to move pieces of the 
> > project that are generic to mainline.
> 
> Yeah.  It seems to have been reviewed to death.  Is it ready to
> be applied yet?

I would just say that this could be seen rather as a driver tracing
interface than a general purpose tracing interface. Therefore, maybe the
name is a bit misleading ? And yes, what is there is good, but it does
not seem to be a replacement for a generic kernel tracer.

My suggestions to turn it into a more suitable interface for a generic
tracer are summarized in this email:
http://lkml.org/lkml/2007/9/15/136

Mathieu

-- 
Mathieu Desnoyers
Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68

  reply	other threads:[~2007-09-18 17:55 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
2007-09-18 17:13       ` Andrew Morton
2007-09-18 17:55         ` Mathieu Desnoyers [this message]
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=20070918175521.GA2915@Krystal \
    --to=mathieu.desnoyers@polymtl.ca \
    --cc=akpm@linux-foundation.org \
    --cc=dwilder@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prasadav@us.ibm.com \
    --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