All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: acme@kernel.org, jolsa@kernel.org, linux-kernel@vger.kernel.org,
	Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 2/2] perf, tools: Add documentation for perf user event parameters
Date: Thu, 13 Oct 2016 13:33:05 +0200	[thread overview]
Message-ID: <20161013113305.GB8036@krava> (raw)
In-Reply-To: <1476306127-19721-2-git-send-email-andi@firstfloor.org>

On Wed, Oct 12, 2016 at 02:02:07PM -0700, Andi Kleen wrote:
> From: Andi Kleen <ak@linux.intel.com>
> 
> There was no proper documention for the user parameters for
> events that the perf parser implements. Document them all
> in the perf list manpage.
> 
> Signed-off-by: Andi Kleen <ak@linux.intel.com>
> ---
>  tools/perf/Documentation/perf-list.txt | 42 ++++++++++++++++++++++++++++++++++
>  1 file changed, 42 insertions(+)
> 
> diff --git a/tools/perf/Documentation/perf-list.txt b/tools/perf/Documentation/perf-list.txt
> index 41857cce5e86..511adc684148 100644
> --- a/tools/perf/Documentation/perf-list.txt
> +++ b/tools/perf/Documentation/perf-list.txt
> @@ -119,6 +119,48 @@ be specified as
>  
>    perf stat -e cpu/event=0xa8,umask=0x1,name=LSD.UOPS_CYCLES,cmask=1/ ...
>  
> +EVENT PARAMETERS
> +----------------
> +
> +The pmu// syntax in perf uses parameters to configure the event for the
> +PMU.
> +
> +For a list of available parameters for each PMU please use
> +
> +  ls /sys/devices/*/format
> +
> +Common parameters are
> +
> +. event=NUM: Event code
> +. umask=NUM: Event umask
> +
> +In addition perf supports some extra parameters to further configure then
> +event
> +
> +. name=name: Use name to display the event in perf
> +. period=NUM: Use sampling period NUM for the event. Similar to the -c parameter,
> +but only applies to this event.  Only valid for perf record and top.
> +. freq=NUM:  Use sampling frequency NUM for the event. Similar to the -c parameter,
> +but only applies to this event.  Only valid for perf record and top.
> +. branch_type=TYPE: Enable last branch sampling for event. TYPE is the same
> +as the argument to perf record's -j option. Use any to be equivalent to -b.
> +when no is specified branch sampling is disabled for this event. Only valid
> +for perf record and top.
> +. time=NUM:  When NUM is non zero collect a time stamp for the event.
> +. call-graph=type: Enable call graph mode for the event. When no is specified call
> +graph is disabled. The parameters are the as to the --call-graph option of
> +perf record. Only valid for perf record and top.
> +. stack-size=BYTES: For dwarf unwinding call graph mode limit the number of stack
> +bytes collected to BYTES.
> +. max-stack=NUM:  For call graph mode limit the number of entries to NUM.
> +. inherit:  Inherit the event to child processes.
> +. no-inherit: Do not inherit the event to child processes.
> +. overwrite: Enable overwrite mode in the perf buffer.
> +. no-overwrite: Do not enable overwrite mode in the perf buffer.
> +. config=NUM: Configure config parameter in perf event attribute.
> +. config1=NUM:  Configure config1 parameter in perf event attribute.
> +. config2=NUM:  Configure config2 parameter in perf event attribute.

we already have some description of these in perf-record.. we might want
to keep just one and have the other one point to it

thanks,
jirka

  reply	other threads:[~2016-10-13 11:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-12 21:02 [PATCH 1/2] perf, tools: Implement branch_type event parameter Andi Kleen
2016-10-12 21:02 ` [PATCH 2/2] perf, tools: Add documentation for perf user event parameters Andi Kleen
2016-10-13 11:33   ` Jiri Olsa [this message]
2016-10-13 11:32 ` [PATCH 1/2] perf, tools: Implement branch_type event parameter Jiri Olsa
2016-10-24 18:56 ` [tip:perf/core] perf " tip-bot for Andi Kleen

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=20161013113305.GB8036@krava \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=andi@firstfloor.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.