From: "Kulkarni, Ganapatrao" <Ganapatrao.Kulkarni@cavium.com>
To: "firstname.lastname@example.org" <email@example.com>,
Cc: "Will.Deacon@arm.com" <Will.Deacon@arm.com>,
"Nair, Jayachandran" <Jayachandran.Nair@cavium.com>,
"Richter, Robert" <Robert.Richter@cavium.com>,
"Lomovtsev, Vadim" <Vadim.Lomovtsev@cavium.com>,
Jan Glauber <Jan.Glauber@cavium.com>,
Subject: [PATCH v7 1/2] perf, uncore: Adding documentation for ThunderX2 pmu uncore driver
Date: Thu, 25 Oct 2018 05:59:20 +0000 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
The SoC has PMU support in its L3 cache controller (L3C) and in the
DDR4 Memory Controller (DMC).
Signed-off-by: Ganapatrao Kulkarni <email@example.com>
Documentation/perf/thunderx2-pmu.txt | 106 +++++++++++++++++++++++++++
1 file changed, 106 insertions(+)
create mode 100644 Documentation/perf/thunderx2-pmu.txt
diff --git a/Documentation/perf/thunderx2-pmu.txt b/Documentation/perf/thunderx2-pmu.txt
new file mode 100644
@@ -0,0 +1,106 @@
+Cavium ThunderX2 SoC Performance Monitoring Unit (PMU UNCORE)
+ThunderX2 SoC PMU consists of independent system wide per Socket PMUs such
+as Level 3 Cache(L3C) and DDR4 Memory Controller(DMC).
+DMC has 8 interleave channels and L3C has 16 interleave tiles. Events are
+sampled for default channel(i.e channel 0) and prorated to total number of
+DMC and L3C, Each PMU supports up to 4 counters. Counters are independently
+programmable and can be started and stopped individually. Each counter can
+be set to sample specific perf events. Counters are 32 bit and do not support
+overflow interrupt; they are sampled at every 2 seconds.
+PMU UNCORE (perf) driver:
+The thunderx2-pmu driver registers several perf PMUs for DMC and L3C devices.
+Each of the PMUs provides description of its available events
+and configuration options in sysfs.
+ see /sys/devices/uncore_<l3c_S/dmc_S/>
+S is socket id.
+Each PMU can be used to sample up to 4 events simultaneously.
+The "format" directory describes format of the config (event ID).
+The "events" directory provides configuration templates for all
+supported event types that can be used with perf tool.
+For example, "uncore_dmc_0/cnt_cycles/" is an
+equivalent of "uncore_dmc_0/config=0x1/".
+Each perf driver also provides a "cpumask" sysfs attribute, which contains a
+single CPU ID of the processor which is likely to be used to handle all the
+PMU events. It will be the first online CPU from the NUMA node of the PMU device.
+Example for perf tool use:
+perf stat -a -e uncore_dmc_0/cnt_cycles/ sleep 1
+perf stat -a -e \
+uncore_dmc_0/write_txns/ sleep 1
+perf stat -a -e \
+uncore_l3c_0/inv_hit/ sleep 1
+The driver does not support sampling, therefore "perf record" will
+not work. Per-task (without "-a") perf sessions are not supported.
+ Number of Read requests received by the L3 Cache.
+ This include Read as well as Read Exclusives.
+ Number of Read requests received by the L3 cache that were hit
+ in the L3 (Data provided form the L3)
+ Number of Write Backs received by the L3 Cache. These are basically
+ the L2 Evicts and writes from the PCIe Write Cache.
+ This is the Number of Invalidate and Write received by the L3 Cache.
+ Also Writes from IO that did not go through the PCIe Write Cache.
+ This is the Number of Invalidate and Write received by the L3 Cache
+ That were a hit in the L3 Cache.
+ Number of Invalidate request received by the L3 Cache.
+ Number of Invalidate request received by the L3 Cache that were a
+ hit in L3.
+ Number of Evicts that the L3 generated.
+1. Granularity of all these events counter value is cache line length(64 Bytes).
+2. L3C cache Hit Ratio = (read_hit + inv_nwrite_hit + inv_hit) / (read_request + inv_nwrite_request + inv_request)
+ Count cycles (Clocks at the DMC clock rate)
+ Number of 64 Bytes write transactions received by the DMC(s)
+ Number of 64 Bytes Read transactions received by the DMC(s)
+ Number of 64 Bytes data transferred to or from DRAM.
next prev parent reply other threads:[~2018-10-25 5:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-25 5:59 [PATCH v7 0/2] Add ThunderX2 SoC Performance Monitoring Unit driver Kulkarni, Ganapatrao
2018-10-25 5:59 ` Kulkarni, Ganapatrao [this message]
2018-10-25 5:59 ` [PATCH v7 2/2] ThunderX2, perf : Add Cavium ThunderX2 SoC UNCORE PMU driver Kulkarni, Ganapatrao
2018-10-25 16:12 ` Randy Dunlap
2018-11-09 10:21 ` Ganapatrao Kulkarni
2018-11-15 22:45 ` Suzuki K Poulose
2018-11-20 5:40 ` Ganapatrao Kulkarni
2018-11-09 10:22 ` [PATCH v7 0/2] Add ThunderX2 SoC Performance Monitoring Unit driver Ganapatrao Kulkarni
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).