From: Masami Hiramatsu <mhiramat@kernel.org>
To: <lecopzer.chen@mediatek.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<corbet@lwn.net>, <mhiramat@kernel.org>,
<srv_heupstream@mediatek.com>, <yj.chiang@mediatek.com>
Subject: Re: [PATCH] Documentation: {u,k}probes: add tracing_on before tracing
Date: Thu, 9 May 2019 22:08:29 +0900 [thread overview]
Message-ID: <20190509220829.42cb21dc0555abe1de98df10@kernel.org> (raw)
In-Reply-To: <1557397876-18153-1-git-send-email-lecopzer.chen@mediatek.com>
On Thu, 9 May 2019 18:31:16 +0800
<lecopzer.chen@mediatek.com> wrote:
> From: Lecopzer Chen <lecopzer.chen@mediatek.com>
>
> After following the document step by step, the `cat trace` can't be
> worked without enabling tracing_on and might mislead newbies about
> the functionality.
OK, but isn't tracing_on enabled by default?
Anyway, it looks good to me (for making sure the trace is enabled).
Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
Thanks!
>
> Signed-off-by: Lecopzer Chen <lecopzer.chen@mediatek.com>
> ---
> Documentation/trace/kprobetrace.rst | 6 ++++++
> Documentation/trace/uprobetracer.rst | 7 ++++++-
> 2 files changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/trace/kprobetrace.rst b/Documentation/trace/kprobetrace.rst
> index 235ce2ab131a..baa3c42ba2f4 100644
> --- a/Documentation/trace/kprobetrace.rst
> +++ b/Documentation/trace/kprobetrace.rst
> @@ -189,6 +189,12 @@ events, you need to enable it.
> echo 1 > /sys/kernel/debug/tracing/events/kprobes/myprobe/enable
> echo 1 > /sys/kernel/debug/tracing/events/kprobes/myretprobe/enable
>
> +Use the following command to start tracing in an interval.
> +::
> + # echo 1 > tracing_on
> + Open something...
> + # echo 0 > tracing_on
> +
> And you can see the traced information via /sys/kernel/debug/tracing/trace.
> ::
>
> diff --git a/Documentation/trace/uprobetracer.rst b/Documentation/trace/uprobetracer.rst
> index 4346e23e3ae7..0b21305fabdc 100644
> --- a/Documentation/trace/uprobetracer.rst
> +++ b/Documentation/trace/uprobetracer.rst
> @@ -152,10 +152,15 @@ events, you need to enable it by::
>
> # echo 1 > events/uprobes/enable
>
> -Lets disable the event after sleeping for some time.
> +Lets start tracing, sleep for some time and stop tracing.
> ::
>
> + # echo 1 > tracing_on
> # sleep 20
> + # echo 0 > tracing_on
> +
> +Also, you can disable the event by::
> +
> # echo 0 > events/uprobes/enable
>
> And you can see the traced information via /sys/kernel/debug/tracing/trace.
> --
> 2.18.0
>
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2019-05-09 13:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 10:31 [PATCH] Documentation: {u,k}probes: add tracing_on before tracing lecopzer.chen
2019-05-09 13:08 ` Masami Hiramatsu [this message]
2019-05-10 4:19 ` Lecopzer Chen
2019-06-07 17:57 ` Jonathan Corbet
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=20190509220829.42cb21dc0555abe1de98df10@kernel.org \
--to=mhiramat@kernel.org \
--cc=corbet@lwn.net \
--cc=lecopzer.chen@mediatek.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srv_heupstream@mediatek.com \
--cc=yj.chiang@mediatek.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