From: James Clark <james.clark@arm.com>
To: suzuki.poulose@arm.com, mathieu.poirier@linaro.org,
coresight@lists.linaro.org, leo.yan@linaro.com,
mike.leach@linaro.org
Cc: James Clark <james.clark@arm.com>, Leo Yan <leo.yan@linaro.org>,
John Garry <john.garry@huawei.com>, Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: [PATCH v2 4/6] Documentation: coresight: Turn numbered subsections into real subsections
Date: Thu, 13 Jan 2022 09:10:53 +0000 [thread overview]
Message-ID: <20220113091056.1297982-5-james.clark@arm.com> (raw)
In-Reply-To: <20220113091056.1297982-1-james.clark@arm.com>
This is to allow them to be referenced in a later commit. There was
also a mistake where sysFS was introduced as section 2, but numbered
as section 1. And vice versa for 'Using perf framework'. This can't
happen with unnumbered sections.
Signed-off-by: James Clark <james.clark@arm.com>
---
Documentation/trace/coresight/coresight.rst | 17 ++++++++++++-----
1 file changed, 12 insertions(+), 5 deletions(-)
diff --git a/Documentation/trace/coresight/coresight.rst b/Documentation/trace/coresight/coresight.rst
index a15571d96cc8..db66ff45ff4c 100644
--- a/Documentation/trace/coresight/coresight.rst
+++ b/Documentation/trace/coresight/coresight.rst
@@ -339,7 +339,8 @@ Preference is given to the former as using the sysFS interface
requires a deep understanding of the Coresight HW. The following sections
provide details on using both methods.
-1) Using the sysFS interface:
+Using the sysFS interface
+~~~~~~~~~~~~~~~~~~~~~~~~~
Before trace collection can start, a coresight sink needs to be identified.
There is no limit on the amount of sinks (nor sources) that can be enabled at
@@ -446,7 +447,8 @@ wealth of possibilities that coresight provides.
Instruction 0 0x8026B588 E8BD8000 true LDM sp!,{pc}
Timestamp Timestamp: 17107041535
-2) Using perf framework:
+Using perf framework
+~~~~~~~~~~~~~~~~~~~~
Coresight tracers are represented using the Perf framework's Performance
Monitoring Unit (PMU) abstraction. As such the perf framework takes charge of
@@ -495,7 +497,11 @@ More information on the above and other example on how to use Coresight with
the perf tools can be found in the "HOWTO.md" file of the openCSD gitHub
repository [#third]_.
-2.1) AutoFDO analysis using the perf tools:
+Advanced perf framework usage
+-----------------------------
+
+AutoFDO analysis using the perf tools
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
perf can be used to record and analyze trace of programs.
@@ -513,7 +519,8 @@ The --itrace option controls the type and frequency of synthesized events
Note that only 64-bit programs are currently supported - further work is
required to support instruction decode of 32-bit Arm programs.
-2.2) Tracing PID
+Tracing PID
+~~~~~~~~~~~
The kernel can be built to write the PID value into the PE ContextID registers.
For a kernel running at EL1, the PID is stored in CONTEXTIDR_EL1. A PE may
@@ -547,7 +554,7 @@ wants to trace PIDs for both host and guest, the two configs "contextid1" and
Generating coverage files for Feedback Directed Optimization: AutoFDO
----------------------------------------------------------------------
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'perf inject' accepts the --itrace option in which case tracing data is
removed and replaced with the synthesized events. e.g.
--
2.28.0
next prev parent reply other threads:[~2022-01-13 9:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 9:10 [PATCH v2 0/6] coresight: Add config flag to enable branch broadcast James Clark
2022-01-13 9:10 ` [PATCH v2 1/6] " James Clark
2022-01-21 12:43 ` Mike Leach
2022-01-28 11:19 ` Suzuki K Poulose
2022-02-02 20:25 ` Mike Leach
2022-03-11 14:58 ` James Clark
2022-03-11 15:56 ` Mike Leach
2022-04-22 10:18 ` James Clark
2022-05-04 9:46 ` Suzuki K Poulose
2022-01-13 9:10 ` [PATCH v2 2/6] coresight: Fail to open with return stacks if they are unavailable James Clark
2022-01-21 12:42 ` Mike Leach
2022-01-28 11:24 ` Suzuki K Poulose
2022-03-11 14:52 ` James Clark
2022-03-11 15:53 ` Mike Leach
2022-04-22 10:09 ` James Clark
2022-01-13 9:10 ` [PATCH v2 3/6] perf cs-etm: Update deduction of TRCCONFIGR register for branch broadcast James Clark
2022-01-21 12:44 ` Mike Leach
2022-01-28 11:25 ` Suzuki K Poulose
2022-02-15 14:52 ` Arnaldo Carvalho de Melo
2022-01-13 9:10 ` James Clark [this message]
2022-01-21 12:47 ` [PATCH v2 4/6] Documentation: coresight: Turn numbered subsections into real subsections Mike Leach
2022-01-28 11:26 ` Suzuki K Poulose
2022-01-13 9:10 ` [PATCH v2 5/6] Documentation: coresight: Link config options to existing documentation James Clark
2022-01-21 12:49 ` Mike Leach
2022-01-13 9:10 ` [PATCH v2 6/6] Documentation: coresight: Expand branch broadcast documentation James Clark
2022-01-21 12:50 ` Mike Leach
2022-01-27 20:26 ` [PATCH v2 0/6] coresight: Add config flag to enable branch broadcast Mathieu Poirier
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=20220113091056.1297982-5-james.clark@arm.com \
--to=james.clark@arm.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=coresight@lists.linaro.org \
--cc=john.garry@huawei.com \
--cc=jolsa@redhat.com \
--cc=leo.yan@linaro.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=namhyung@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=will@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 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).