From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Rob Landley <rob@landley.net>,
Steven Rostedt <rostedt@goodmis.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: Remove text on tracepoint samples
Date: Fri, 15 Mar 2013 11:05:31 -0400 [thread overview]
Message-ID: <20130315150531.GA1382@Krystal> (raw)
In-Reply-To: <1363359483.1335.110.camel@x61.thuisdomein>
* Paul Bolle (pebolle@tiscali.nl) wrote:
> The tracepoint sample code got removed. Remove a few lines on its usage
> too.
>
> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
Thanks!
Acked-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> ---
> Documentation/trace/tracepoints.txt | 15 ---------------
> 1 file changed, 15 deletions(-)
>
> diff --git a/Documentation/trace/tracepoints.txt b/Documentation/trace/tracepoints.txt
> index c0e1cee..da49437 100644
> --- a/Documentation/trace/tracepoints.txt
> +++ b/Documentation/trace/tracepoints.txt
> @@ -81,7 +81,6 @@ tracepoint_synchronize_unregister() must be called before the end of
> the module exit function to make sure there is no caller left using
> the probe. This, and the fact that preemption is disabled around the
> probe call, make sure that probe removal and module unload are safe.
> -See the "Probe example" section below for a sample probe module.
>
> The tracepoint mechanism supports inserting multiple instances of the
> same tracepoint, but a single definition must be made of a given
> @@ -100,17 +99,3 @@ core kernel image or in modules.
> If the tracepoint has to be used in kernel modules, an
> EXPORT_TRACEPOINT_SYMBOL_GPL() or EXPORT_TRACEPOINT_SYMBOL() can be
> used to export the defined tracepoints.
> -
> -* Probe / tracepoint example
> -
> -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.
> -
> -Run, as root :
> -modprobe tracepoint-sample (insmod order is not important)
> -modprobe tracepoint-probe-sample
> -cat /proc/tracepoint-sample (returns an expected error)
> -rmmod tracepoint-sample tracepoint-probe-sample
> -dmesg
> --
> 1.7.11.7
>
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2013-03-15 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 14:58 [PATCH] Documentation: Remove text on tracepoint samples Paul Bolle
2013-03-15 15:05 ` Mathieu Desnoyers [this message]
2013-03-18 8:34 ` [PATCH] [TRIVIAL] " Paul Bolle
2013-03-21 1:11 ` Steven Rostedt
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=20130315150531.GA1382@Krystal \
--to=mathieu.desnoyers@efficios.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=rob@landley.net \
--cc=rostedt@goodmis.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