From: David Wilder <dwilder@us.ibm.com>
To: Christoph Hellwig <hch@infradead.org>,
"David J. Wilder" <dwilder@us.ibm.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [Patch 1/2] Trace code and documentation (resend)
Date: Mon, 24 Sep 2007 08:38:34 -0700 [thread overview]
Message-ID: <46F7D9FA.3090108@us.ibm.com> (raw)
In-Reply-To: <20070922093508.GC27827@infradead.org>
Christoph Hellwig wrote:
> On Fri, Sep 21, 2007 at 09:23:28PM -0700, David J. Wilder wrote:
>> My last posting was mangled by my mailer. I hope this one is better.
>> Also corrected Randy's concerns.
>>
>> Please see previous posting for more information:
>> http://lkml.org/lkml/2007/9/19/4 (PATCH 0/2)
>>
>> Note: this patch requires "[Patch 2/2] Relay reset consumed" is applied.
>>
>> ---------<start of patch>------------
>> Trace - Provides tracing primitives
>>
>> Signed-off-by: Tom Zanussi <zanussi@us.ibm.com>
>> Signed-off-by: Martin Hunt <hunt@redhat.com>
>> Signed-off-by: David Wilder <dwilder@us.ibm.com>
>> ---
>> Documentation/trace/src/Makefile | 7 +
>> Documentation/trace/src/README | 18 +
>> Documentation/trace/src/fork_trace.c | 119 +++++++
>> Documentation/trace/trace.txt | 164 ++++++++++
>
> NACK, don't put code into Documentation/. Put it into kernel as it's
> actually useful kernel code.
Are you suggesting moving the example code into kernel? Or complaining
about example code in /Documentation?
And add clone,exec and exit while you're at it.
Hu? A syscall tracer sounds like a nice idea but that is not what I am
trying to accomplish. I will let Systemtap handle that.
next prev parent reply other threads:[~2007-09-24 15:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-22 4:23 [Patch 1/2] Trace code and documentation (resend) David J. Wilder
2007-09-22 9:35 ` Christoph Hellwig
2007-09-24 15:38 ` David Wilder [this message]
2007-09-24 15:41 ` Christoph Hellwig
2007-09-24 16:13 ` Randy Dunlap
2007-09-24 16:32 ` 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=46F7D9FA.3090108@us.ibm.com \
--to=dwilder@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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