From: German Gomez <german.gomez@arm.com>
To: coresight@lists.linaro.org, mathieu.poirier@linaro.org,
suzuki.poulose@arm.com
Cc: james.clark@arm.com, leo.yan@linaro.org, mike.leach@linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, German Gomez <german.gomez@arm.com>
Subject: [PATCH 0/2] coresight: etm4x: Expose default timestamp source in sysfs
Date: Fri, 29 Apr 2022 13:30:58 +0100 [thread overview]
Message-ID: <20220429123100.268059-1-german.gomez@arm.com> (raw)
Hi,
I'm Sending this sysfs addition to the etm4x driver in order to expose
the timestamp source of the trace (given by the TRFCR_ELx.TS register).
As mentioned in [1/2], having this information is useful for assigning
Kernel times to the perf samples.
Thanks,
German
German Gomez (3):
coresight: etm4x: Expose default timestamp source in sysfs
coresight: etm4x: docs: Add documentation for 'ts_source' sysfs
interface
perf cs_etm: Store ts_source in AUXTRACE_INFO fields
.../testing/sysfs-bus-coresight-devices-etm4x | 8 +++
.../coresight/coresight-etm4x-reference.rst | 14 ++++
arch/arm64/include/asm/sysreg.h | 1 +
.../coresight/coresight-etm4x-sysfs.c | 34 ++++++++++
tools/perf/arch/arm/util/cs-etm.c | 64 +++++++++++++++++--
tools/perf/util/cs-etm.c | 61 +++++++++---------
tools/perf/util/cs-etm.h | 13 +++-
7 files changed, 159 insertions(+), 36 deletions(-)
--
2.25.1
next reply other threads:[~2022-04-29 12:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 12:30 German Gomez [this message]
2022-04-29 12:30 ` [PATCH 1/2] " German Gomez
2022-04-29 16:28 ` Leo Yan
2022-05-02 16:49 ` Mathieu Poirier
2022-04-29 12:31 ` [PATCH 2/2] coresight: etm4x: docs: Add documentation for 'ts_source' sysfs interface German Gomez
2022-05-02 16:45 ` 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=20220429123100.268059-1-german.gomez@arm.com \
--to=german.gomez@arm.com \
--cc=coresight@lists.linaro.org \
--cc=james.clark@arm.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=suzuki.poulose@arm.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®