From: Jiri Olsa <jolsa@redhat.com>
To: Sangwon Hong <qpakzk@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Taeung Song <treeze.taeung@gmail.com>
Subject: Re: [PATCH] perf mem: Document uncorrect and missing options
Date: Sun, 22 Apr 2018 18:18:24 +0200 [thread overview]
Message-ID: <20180422161824.GA2123@krava> (raw)
In-Reply-To: <1524382146-19609-1-git-send-email-qpakzk@gmail.com>
On Sun, Apr 22, 2018 at 04:29:06PM +0900, Sangwon Hong wrote:
SNIP
> -C::
> ---cpu-list::
> - Restrict dump of raw samples to those provided via this option. Note that the same
> - option can be passed in record mode. It will be interpreted the same way as perf
> - record.
> +--cpu=<cpu>::
> + Monitor only on the list of CPUs provided. Multiple CPUs can be provided as a
> + comma-separated list with no space: 0,1. Ranges of CPUs are specified with -: 0-2. Default
> + is to monitor all CPUS.
> +-U::
> +--hide-unresolved::
> + Only display entries resolved to a symbol.
> +
> +-p::
> +--phys-data::
> + Record/Report sample physical addresses
> +
> +RECORD OPTIONS
> +--------------
> +-e::
> +--event <event>::
> + Event selector. Use 'perf mem record -e list' to list available events.
extra white space at the end of above line..
other than that it looks ok, thanks for doing this
Acked-by: Jiri Olsa <jolsa@kernel.org>
thanks,
jirka
next prev parent reply other threads:[~2018-04-22 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-22 7:29 [PATCH] perf mem: Document uncorrect and missing options Sangwon Hong
2018-04-22 16:18 ` Jiri Olsa [this message]
2018-04-26 5:55 ` [tip:perf/urgent] perf mem: Document incorrect " tip-bot for Sangwon Hong
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=20180422161824.GA2123@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=qpakzk@gmail.com \
--cc=treeze.taeung@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 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.