public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: hotran@apm.com (Hoan Tran)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] Documentation: perf: xgene: Add support for SoC PMU of next generation of X-Gene
Date: Tue, 14 Mar 2017 11:06:51 -0700	[thread overview]
Message-ID: <1489514812-19671-2-git-send-email-hotran@apm.com> (raw)
In-Reply-To: <1489514812-19671-1-git-send-email-hotran@apm.com>

This patch adds support for SoC-wide (AKA uncore) Performance Monitoring
Unit in the next generation of X-Gene SoC.

Signed-off-by: Hoan Tran <hotran@apm.com>
---
 Documentation/perf/xgene-pmu.txt | 17 +++++++++++------
 1 file changed, 11 insertions(+), 6 deletions(-)

diff --git a/Documentation/perf/xgene-pmu.txt b/Documentation/perf/xgene-pmu.txt
index d7cff44..51f8179 100644
--- a/Documentation/perf/xgene-pmu.txt
+++ b/Documentation/perf/xgene-pmu.txt
@@ -23,12 +23,17 @@ equivalent of "l3c0/config=0x0b/".
 Most of the SoC PMU has a specific list of agent ID used for monitoring
 performance of a specific datapath. For example, agents of a L3 cache can be
 a specific CPU or an I/O bridge. Each PMU has a set of 2 registers capable of
-masking the agents from which the request come from. If the bit with
-the bit number corresponding to the agent is set, the event is counted only if
-it is caused by a request from that agent. Each agent ID bit is inversely mapped
-to a corresponding bit in "config1" field. By default, the event will be
-counted for all agent requests (config1 = 0x0). For all the supported agents of
-each PMU, please refer to APM X-Gene User Manual.
+masking the agents from which the request come from. If an agent is enabled,
+the event is counted only if it is caused by a request from that agent.
+ - With SoC PMU version 1 and 2, each agent ID has an enable bit which is
+inversely mapped to a corresponding bit in "config1" field. The value by
+default of config1 is 0.
+ - With Soc PMU version 3, agent ID enable mask is encoded and mapped into
+"config1" field without inversion. The value by default of "config1" is
+defined corresponding to each SoC PMU type.
+By default, the event will be counted for all agent requests. For all the
+supported agents of each PMU and agent configuration, please refer to
+APM X-Gene User Manual.
 
 Each perf driver also provides a "cpumask" sysfs attribute, which contains a
 single CPU ID of the processor which will be used to handle all the PMU events.
-- 
1.9.1

  reply	other threads:[~2017-03-14 18:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-14 18:06 [PATCH 0/2] perf: xgene: Add support for SoC PMU of next generation of X-Gene Hoan Tran
2017-03-14 18:06 ` Hoan Tran [this message]
2017-03-14 19:05   ` [PATCH 1/2] Documentation: " Mark Rutland
2017-03-14 18:06 ` [PATCH 2/2] " Hoan Tran
2017-03-14 19:57   ` Mark Rutland
2017-03-30 17:53     ` Hoan Tran

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=1489514812-19671-2-git-send-email-hotran@apm.com \
    --to=hotran@apm.com \
    --cc=linux-arm-kernel@lists.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