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, akpm@linux-foundation.org Cc: randy.dunlap@oracle.com, hch@infradead.org, systemtap@sources.redhat.com Subject: [PATCH 0/3] A kernel tracing interface Date: Tue, 02 Oct 2007 09:33:16 -0700 [thread overview] Message-ID: <1191342796.31351.8.camel@lc4eb748232119.ibm.com> (raw) [PATCH 0/3] A kernel tracing interface - (updated) These patches provide a kernel tracing interface called "trace". (update) Fixed a notation in the trace documentation as pointed out by Randy Dunlap. Updated references to prerequisite patches. 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-rc8-mm2 Summary of patches: [patch 1/3] Trace code and documentation [patch 2/3] Relay Reset Consumed [patch 3/3] Trace sample Note: Patch 2/3 provides a service used by patch 1/3 thus must be applied first or at the same time. Note: The following patches must be applied prior to 3/3. [patch 3/5] Add samples subdir http://lkml.org/lkml/2007/9/28/178 [patch 4/5] Linux Kernel Markers - Samples http://lkml.org/lkml/2007/9/28/189 Signed-off-by: David Wilder <dwilder@us.ibm.com>
next reply other threads:[~2007-10-02 16:33 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-10-02 16:33 David J. Wilder [this message] 2007-10-02 18:55 [PATCH 0/3] A kernel tracing interface David J. Wilder 2007-11-13 1:02 David J. Wilder 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
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=1191342796.31351.8.camel@lc4eb748232119.ibm.com \ --to=dwilder@us.ibm.com \ --cc=akpm@linux-foundation.org \ --cc=hch@infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=randy.dunlap@oracle.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: linkBe 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).