From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Breno Leitao <leitao@linux.vnet.ibm.com>, Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: improving tracepoints.txt
Date: Tue, 6 Oct 2009 16:12:20 -0400 [thread overview]
Message-ID: <20091006201220.GA3934@Krystal> (raw)
In-Reply-To: <1254859771-8873-1-git-send-email-leitao@linux.vnet.ibm.com>
* Breno Leitao (leitao@linux.vnet.ibm.com) wrote:
> After reading the tracepoints.txt documentation, I tried to
> follow the instructions to run the sample, but just assigning
> CONFIG_SAMPLE_TRACEPOINTS=m wasn't enough to generate the tracepoints
> samples. I also need to set CONFIG_SAMPLES=y, otherwise nothing
> happens.
>
> So, this silly patch explicit says that CONFIG_SAMPLES should be set to
> compile those files.
>
> Signed-off-by: Breno Leitao <leitao@linux.vnet.ibm.com>
Yep, good idea. Thanks !
Acked-by: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
> ---
> Documentation/trace/tracepoints.txt | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/Documentation/trace/tracepoints.txt b/Documentation/trace/tracepoints.txt
> index c0e1cee..d380250 100644
> --- a/Documentation/trace/tracepoints.txt
> +++ b/Documentation/trace/tracepoints.txt
> @@ -106,7 +106,7 @@ used to export the defined tracepoints.
> See the example provided in samples/tracepoints
>
> Compile them with your kernel. They are built during 'make' (not
> -'make modules') when CONFIG_SAMPLE_TRACEPOINTS=m.
> +'make modules') when CONFIG_SAMPLE=y and CONFIG_SAMPLE_TRACEPOINTS=m.
>
> Run, as root :
> modprobe tracepoint-sample (insmod order is not important)
> --
> 1.6.0.4
>
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next prev parent reply other threads:[~2009-10-06 20:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 20:09 [PATCH] Documentation: improving tracepoints.txt Breno Leitao
2009-10-06 20:12 ` Mathieu Desnoyers [this message]
2009-10-06 20:27 ` Christoph Hellwig
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=20091006201220.GA3934@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=leitao@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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