LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "David J. Wilder" <dwilder@us.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: systemtap@sources.redhat.com
Subject: [PATCH 0/3] A kernel tracing interface
Date: Mon, 12 Nov 2007 17:02:10 -0800	[thread overview]
Message-ID: <1194915731.913.16.camel@lc4eb748232119.ibm.com> (raw)

These patches provide a kernel tracing interface called "trace".

ChangeLog:
-Added a new example that demonstrates per-cpu continuous tracing
 of data generated by 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.

Patches are against 2.6.23-mm1

Summary of patches:
[patch 1/3]  Relay Reset Consumed
[patch 2/3]  Trace code and documentation
[patch 3/3]  Trace samples

Note: Patch 1/3 provides a service used by patch 2/3
thus must be applied first or at the same time.

Note: The sem_watch example requires that  /lib/semaphore-sleepers.c
is patched to add several markers around the semaphore primitives,
see the patch at: http://lkml.org/lkml/2007/11/12/279

Signed-off-by: David Wilder <dwilder@us.ibm.com>



             reply	other threads:[~2007-11-13  1:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13  1:02 David J. Wilder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-02-26 22:38 David J. Wilder
2008-02-28 10:04 ` Andrew Morton
2008-02-28 19:40   ` David Wilder
2008-02-29  5:36     ` K. Prasad
2008-02-29 12:08       ` K. Prasad
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:
  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=1194915731.913.16.camel@lc4eb748232119.ibm.com \
    --to=dwilder@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=systemtap@sources.redhat.com \
    --subject='Re: [PATCH 0/3] A kernel tracing interface' \
    /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

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).