From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
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,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH] perf script: add -S/--symbols documentation
Date: Thu, 2 Apr 2020 15:46:56 -0300 [thread overview]
Message-ID: <20200402184656.GA23243@kernel.org> (raw)
In-Reply-To: <20200402174130.140319-1-irogers@google.com>
Em Thu, Apr 02, 2020 at 10:41:30AM -0700, Ian Rogers escreveu:
> Capture both that this option exists and that symbols can be hexadecimal
> addresses.
Thanks, applied.
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/perf/Documentation/perf-script.txt | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/tools/perf/Documentation/perf-script.txt b/tools/perf/Documentation/perf-script.txt
> index 99a9853a11ba..963487e82edc 100644
> --- a/tools/perf/Documentation/perf-script.txt
> +++ b/tools/perf/Documentation/perf-script.txt
> @@ -412,6 +412,14 @@ include::itrace.txt[]
> --xed::
> Run xed disassembler on output. Requires installing the xed disassembler.
>
> +-S::
> +--symbols=symbol[,symbol...]::
> + Only consider the listed symbols. Symbols are typically a name
> + but they may also be hexadecimal address.
> +
> + For example, to select the symbol noploop or the address 0x4007a0:
> + perf script --symbols=noploop,0x4007a0
> +
> --call-trace::
> Show call stream for intel_pt traces. The CPUs are interleaved, but
> can be filtered with -C.
> --
> 2.26.0.rc2.310.g2932bb562d-goog
>
--
- Arnaldo
next prev parent reply other threads:[~2020-04-02 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 17:41 [PATCH] perf script: add -S/--symbols documentation Ian Rogers
2020-04-02 18:46 ` Arnaldo Carvalho de Melo [this message]
2020-04-04 8:41 ` [tip: perf/urgent] " tip-bot2 for Ian Rogers
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=20200402184656.GA23243@kernel.org \
--to=arnaldo.melo@gmail.com \
--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=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).