public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@gmail.com>
To: Stanislav Fomichev <stfomichev@yandex-team.ru>
Cc: acme@kernel.org, artagnon@gmail.com, jolsa@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] perf timechart: fix documentation
Date: Tue, 10 Jun 2014 16:14:58 +0900	[thread overview]
Message-ID: <87bnu1b5hp.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <1402305672-2630-2-git-send-email-stfomichev@yandex-team.ru> (Stanislav Fomichev's message of "Mon, 9 Jun 2014 13:21:11 +0400")

Hi Stanislav,

On Mon,  9 Jun 2014 13:21:11 +0400, Stanislav Fomichev wrote:
> Move options away from examples.

I think it's better to move RECORD OPTIONS as well.

Thanks,
Namhyung


>
> Signed-off-by: Stanislav Fomichev <stfomichev@yandex-team.ru>
> ---
>  tools/perf/Documentation/perf-timechart.txt | 23 +++++++++++------------
>  1 file changed, 11 insertions(+), 12 deletions(-)
>
> diff --git a/tools/perf/Documentation/perf-timechart.txt b/tools/perf/Documentation/perf-timechart.txt
> index bc5990c33dc0..fab20d4504d2 100644
> --- a/tools/perf/Documentation/perf-timechart.txt
> +++ b/tools/perf/Documentation/perf-timechart.txt
> @@ -43,6 +43,17 @@ TIMECHART OPTIONS
>  
>  --symfs=<directory>::
>          Look for files with symbols relative to this directory.
> +-n::
> +--proc-num::
> +        Print task info for at least given number of tasks.
> +-t::
> +--topology::
> +        Sort CPUs according to topology.
> +--highlight=<duration_nsecs|task_name>::
> +	Highlight tasks (using different color) that run more than given
> +	duration or tasks with given name. If number is given it's interpreted
> +	as number of nanoseconds. If non-numeric string is given it's
> +	interpreted as task name.
>  
>  EXAMPLES
>  --------
> @@ -64,18 +75,6 @@ Record system-wide timechart:
>  
>    $ perf timechart --highlight gcc
>  
> --n::
> ---proc-num::
> -        Print task info for at least given number of tasks.
> --t::
> ---topology::
> -        Sort CPUs according to topology.
> ---highlight=<duration_nsecs|task_name>::
> -	Highlight tasks (using different color) that run more than given
> -	duration or tasks with given name. If number is given it's interpreted
> -	as number of nanoseconds. If non-numeric string is given it's
> -	interpreted as task name.
> -
>  RECORD OPTIONS
>  --------------
>  -P::

  reply	other threads:[~2014-06-10  7:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-09  9:21 [PATCH 0/2] perf timechart fix & io mode Stanislav Fomichev
2014-06-09  9:21 ` [PATCH 1/2] perf timechart: fix documentation Stanislav Fomichev
2014-06-10  7:14   ` Namhyung Kim [this message]
2014-06-10  9:52     ` [PATCH 1/2 v2] " Stanislav Fomichev
2014-06-12 12:04       ` [tip:perf/core] perf timechart: Reflow documentation tip-bot for Stanislav Fomichev
2014-06-09  9:21 ` [PATCH 2/2] perf timechart: implement IO mode Stanislav Fomichev
2014-06-09 19:25   ` Arnaldo Carvalho de Melo
2014-06-10  7:28   ` Namhyung Kim
2014-06-10  7:50   ` Namhyung Kim
2014-06-10  9:08     ` Stanislav Fomichev

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=87bnu1b5hp.fsf@sejong.aot.lge.com \
    --to=namhyung@gmail.com \
    --cc=acme@kernel.org \
    --cc=artagnon@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stfomichev@yandex-team.ru \
    /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