From: David Wilder <dwilder@us.ibm.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
hch@infradead.org, systemtap@sources.redhat.com
Subject: Re: [patch 3/3] Trace sample
Date: Tue, 02 Oct 2007 10:41:28 -0700 [thread overview]
Message-ID: <470282C8.5020105@us.ibm.com> (raw)
In-Reply-To: <20071002101032.55403fef.randy.dunlap@oracle.com>
Randy Dunlap wrote:
> On Tue, 02 Oct 2007 09:33:25 -0700 David J. Wilder wrote:
>
>> Trace example - Adds the trace example to samples/
>>
>> Signed-off-by: David Wilder <dwilder@us.ibm.com>
>> ---
>> samples/Kconfig | 6 ++
>> samples/Makefile | 1 +
>> samples/trace/Makefile | 4 +
>> samples/trace/fork_trace.c | 132 ++++++++++++++++++++++++++++++++++++++++++++
>> 4 files changed, 143 insertions(+), 0 deletions(-)
>>
>> diff --git a/samples/Kconfig b/samples/Kconfig
>> index 57bb223..e11c806 100644
>> --- a/samples/Kconfig
>> +++ b/samples/Kconfig
>> @@ -13,4 +13,10 @@ config SAMPLE_MARKERS
>> help
>> This build markers example modules.
>>
>> +config SAMPLE_TRACE
>> + tristate "Build trace example -- loadable modules only"
>> + depends on TRACE && m
>
> The sample code uses kprobes, so this should also be:
>
> depends on KPROBES
>
> Is (are?) kprobes always needed for trace?
No, just the sample.
If so, the documentation
> probably should mention that also (along with relay & debugfs).
>
...
next prev parent reply other threads:[~2007-10-02 17:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 16:33 [patch 3/3] Trace sample David J. Wilder
2007-10-02 17:10 ` Randy Dunlap
2007-10-02 17:41 ` David Wilder [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-03 23:52 David J. Wilder
2008-02-26 22:38 David J. Wilder
2008-03-10 21:55 ` Greg KH
2007-10-02 18:55 David J. Wilder
2007-09-26 18:22 David J. Wilder
2007-09-26 18:39 ` Randy Dunlap
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=470282C8.5020105@us.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: 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