linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH] perf kmem: Improve man page for record options
Date: Fri, 8 Oct 2021 16:10:25 -0300	[thread overview]
Message-ID: <YWCXoRis0BhKJCYC@kernel.org> (raw)
In-Reply-To: <20210922212031.485950-1-irogers@google.com>

Em Wed, Sep 22, 2021 at 02:20:31PM -0700, Ian Rogers escreveu:
> Since:
> https://lore.kernel.org/lkml/20200708183919.4141023-1-irogers@google.com/
> The output option works for 'perf kmem', however, it must appear after
> 'record'. This is different to 'stat' where '-i' for the input must
> appear before. Try to capture this complication in the man page.

Thanks, applied.

- Arnaldo

 
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
>  tools/perf/Documentation/perf-kmem.txt | 13 ++++++++-----
>  1 file changed, 8 insertions(+), 5 deletions(-)
> 
> diff --git a/tools/perf/Documentation/perf-kmem.txt b/tools/perf/Documentation/perf-kmem.txt
> index 85b8ac695c87..f378ac59353d 100644
> --- a/tools/perf/Documentation/perf-kmem.txt
> +++ b/tools/perf/Documentation/perf-kmem.txt
> @@ -8,22 +8,25 @@ perf-kmem - Tool to trace/measure kernel memory properties
>  SYNOPSIS
>  --------
>  [verse]
> -'perf kmem' {record|stat} [<options>]
> +'perf kmem' [<options>] {record|stat}
>  
>  DESCRIPTION
>  -----------
>  There are two variants of perf kmem:
>  
> -  'perf kmem record <command>' to record the kmem events
> -  of an arbitrary workload.
> +  'perf kmem [<options>] record [<perf-record-options>] <command>' to
> +  record the kmem events of an arbitrary workload. Additional 'perf
> +  record' options may be specified after record, such as '-o' to
> +  change the output file name.
>  
> -  'perf kmem stat' to report kernel memory statistics.
> +  'perf kmem [<options>] stat' to report kernel memory statistics.
>  
>  OPTIONS
>  -------
>  -i <file>::
>  --input=<file>::
> -	Select the input file (default: perf.data unless stdin is a fifo)
> +	For stat, select the input file (default: perf.data unless stdin is a
> +	fifo)
>  
>  -f::
>  --force::
> -- 
> 2.33.0.464.g1972c5931b-goog

-- 

- Arnaldo

      reply	other threads:[~2021-10-08 19:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-22 21:20 [PATCH] perf kmem: Improve man page for record options Ian Rogers
2021-10-08 19:10 ` Arnaldo Carvalho de Melo [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=YWCXoRis0BhKJCYC@kernel.org \
    --to=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=eranian@google.com \
    --cc=irogers@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).