From: Tan Xiaojun <tanxiaojun@huawei.com>
To: <peterz@infradead.org>, <mingo@redhat.com>, <acme@kernel.org>,
<alexander.shishkin@linux.intel.com>, <jolsa@redhat.com>,
<namhyung@kernel.org>, <ak@linux.intel.com>,
<adrian.hunter@intel.com>, <yao.jin@linux.intel.com>,
<tmricht@linux.ibm.com>, <brueckner@linux.ibm.com>,
<songliubraving@fb.com>, <gregkh@linuxfoundation.org>,
<kim.phillips@arm.com>, <James.Clark@arm.com>,
<jeremy.linton@arm.com>
Cc: <gengdongjiu@huawei.com>, <wxf.wang@hisilicon.com>,
<liwei391@huawei.com>, <tanxiaojun@huawei.com>,
<huawei.libin@huawei.com>, <linux-kernel@vger.kernel.org>,
<linux-perf-users@vger.kernel.org>
Subject: [RFC v3 3/5] perf report: Add --spe options for arm-spe
Date: Sat, 23 Nov 2019 18:11:16 +0800 [thread overview]
Message-ID: <20191123101118.12635-4-tanxiaojun@huawei.com> (raw)
In-Reply-To: <20191123101118.12635-1-tanxiaojun@huawei.com>
The previous patch added support in "perf report" for some arm-spe
events(llc-miss, tlb-miss, branch-miss, remote_access). This patch adds their help
instructions.
Signed-off-by: Tan Xiaojun <tanxiaojun@huawei.com>
---
tools/perf/Documentation/perf-report.txt | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/tools/perf/Documentation/perf-report.txt b/tools/perf/Documentation/perf-report.txt
index 7315f155803f..188a9477558b 100644
--- a/tools/perf/Documentation/perf-report.txt
+++ b/tools/perf/Documentation/perf-report.txt
@@ -462,6 +462,16 @@ include::itrace.txt[]
To disable decoding entirely, use --no-itrace.
+--spe::
+ Options for decoding arm-spe tracing data. The options are:
+
+ l synthesize llc miss events
+ t synthesize tlb miss events
+ b synthesize branch miss events
+ r synthesize remote access events
+
+ The default is all events i.e. the same as --spe=ltbr
+
--full-source-path::
Show the full path for source files for srcline output.
--
2.17.1
next prev parent reply other threads:[~2019-11-23 9:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-23 10:11 [RFC v3 0/5] perf tools: Add support for some spe events and precise ip Tan Xiaojun
2019-11-23 10:11 ` [RFC v3 1/5] perf tools: Move arm-spe-pkt-decoder.h/c to the new dir Tan Xiaojun
2019-11-23 10:11 ` [RFC v3 2/5] perf tools: Add support for "report" for some spe events Tan Xiaojun
2019-11-23 10:11 ` Tan Xiaojun [this message]
2019-11-23 10:11 ` [RFC v3 4/5] drivers: perf: add some arm " Tan Xiaojun
2019-11-23 10:11 ` [RFC v3 5/5] perf tools: Add support to process multi " Tan Xiaojun
2019-11-29 16:32 ` James Clark
2019-11-30 0:42 ` Tan Xiaojun
2019-12-06 15:48 ` James Clark
2019-12-09 0:46 ` Tan Xiaojun
2019-12-12 15:50 ` James Clark
2019-12-16 3:20 ` Tan Xiaojun
2019-12-02 7:07 ` [RFC v3 0/5] perf tools: Add support for some spe events and precise ip Qi Liu
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=20191123101118.12635-4-tanxiaojun@huawei.com \
--to=tanxiaojun@huawei.com \
--cc=James.Clark@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=brueckner@linux.ibm.com \
--cc=gengdongjiu@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=huawei.libin@huawei.com \
--cc=jeremy.linton@arm.com \
--cc=jolsa@redhat.com \
--cc=kim.phillips@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=liwei391@huawei.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.com \
--cc=tmricht@linux.ibm.com \
--cc=wxf.wang@hisilicon.com \
--cc=yao.jin@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®