From: Steven Rostedt <rostedt@goodmis.org>
To: Wang YanQing <udknight@gmail.com>
Cc: fweisbec@gmail.com, mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH]trace: fix wrong help information about snapshot
Date: Thu, 12 Sep 2013 12:33:47 -0400 [thread overview]
Message-ID: <20130912123347.5bf5de1e@gandalf.local.home> (raw)
In-Reply-To: <20130912150401.GA3960@udknight>
On Thu, 12 Sep 2013 23:04:01 +0800
Wang YanQing <udknight@gmail.com> wrote:
>
> Cat snapshot give me:
> " tracer: nop
>
> * Snapshot is freed *
>
> Snapshot commands:
> echo 0 > snapshot : Clears and frees snapshot buffer
> echo 1 > snapshot : Allocates snapshot buffer, if not already allocated.
> Takes a snapshot of the main buffer.
> echo 2 > snapshot : Clears snapshot buffer (but does not allocate)
> (Doesn't have to be '2' works with any number that
> is not a '0' or '1')"
>
> But after read the code, I found the right information about "echo 2 > snapshot"
> should looks like below:
>
> " echo 2 > snapshot : Clears snapshot buffer (but does not free)
> (Doesn't have to be '2' works with any number that
> is not a '0' or '1')"
Actually, they both are correct:
default:
if (tr->allocated_snapshot) {
if (iter->cpu_file == RING_BUFFER_ALL_CPUS)
tracing_reset_online_cpus(&tr->max_buffer);
else
tracing_reset(&tr->max_buffer, iter->cpu_file);
}
break;
}
It does nothing if it isn't allocated.
Perhaps we need it to say "(but does not allocate or free)"
-- Steve
>
> Signed-off-by: Wang YanQing <udknight@gmail.com>
> ---
> kernel/trace/trace.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
> index 7974ba2..d0da660 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -2760,7 +2760,7 @@ static void show_snapshot_main_help(struct seq_file *m)
> seq_printf(m, "# echo 0 > snapshot : Clears and frees snapshot buffer\n");
> seq_printf(m, "# echo 1 > snapshot : Allocates snapshot buffer, if not already allocated.\n");
> seq_printf(m, "# Takes a snapshot of the main buffer.\n");
> - seq_printf(m, "# echo 2 > snapshot : Clears snapshot buffer (but does not allocate)\n");
> + seq_printf(m, "# echo 2 > snapshot : Clears snapshot buffer (but does not free)\n");
> seq_printf(m, "# (Doesn't have to be '2' works with any number that\n");
> seq_printf(m, "# is not a '0' or '1')\n");
> }
prev parent reply other threads:[~2013-09-12 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 15:04 Wang YanQing
2013-09-12 16:33 ` Steven Rostedt [this message]
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=20130912123347.5bf5de1e@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=udknight@gmail.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
all inboxes | Powered by JetHome®