Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:6 as permitted sender) client-ip=2620:137:e000::3:6;
Received-SPF: Pass (protection.outlook.com: domain of amd.com designates
 165.204.84.17 as permitted sender) receiver=protection.outlook.com;
 client-ip=165.204.84.17; helo=SATLEXMB04.amd.com; pr=C
From:   Sandipan Das <sandipan.das@amd.com>
To:     <linux-kernel@vger.kernel.org>, <linux-perf-users@vger.kernel.org>,
        <x86@kernel.org>
CC:     <peterz@infradead.org>, <mingo@redhat.com>, <acme@kernel.org>,
        <mark.rutland@arm.com>, <alexander.shishkin@linux.intel.com>,
        <jolsa@kernel.org>, <namhyung@kernel.org>, <irogers@google.com>,
        <adrian.hunter@intel.com>, <tglx@linutronix.de>, <bp@alien8.de>,
        <dave.hansen@linux.intel.com>, <hpa@zytor.com>,
        <eranian@google.com>, <ananth.narayan@amd.com>,
        <ravi.bangoria@amd.com>, <santosh.shukla@amd.com>,
        <sandipan.das@amd.com>
Subject: [PATCH v2 0/6] perf/x86/amd: Add memory controller events
Date:   Thu, 5 Oct 2023 10:53:10 +0530
Message-ID: <cover.1696425185.git.sandipan.das@amd.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 05 Oct 2023 05:23:35.8825
 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: c19db04e-217c-45cd-78c4-08dbc5633972
X-MS-Exchange-CrossTenant-Id: 3dd8961f-e488-4e60-8e11-a82d994e183d
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=3dd8961f-e488-4e60-8e11-a82d994e183d;Ip=[165.204.84.17];Helo=[SATLEXMB04.amd.com]
X-MS-Exchange-CrossTenant-AuthSource: BL6PEPF0001AB4C.namprd04.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN0PR12MB5930
X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,
	MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED
	autolearn=unavailable autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on pete.vger.email
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (pete.vger.email [0.0.0.0]); Thu, 05 Oct 2023 09:41:01 -0700 (PDT)

Unified Memory Controller (UMC) events were introduced with Zen 4 as a
part of the Performance Monitoring Version 2 (PerfMonV2) enhancements.
Currently, Zen 4 supports up to 12 channels of DDR5 memory and each of
them are controlled by a dedicated UMC. Each UMC, in turn, has its own
set of performance monitoring counters. These counters can provide info
on UMC command activity which in turn can be used to derive utilization
and bandwidth. Using perf tool, users can profile activity either on a
combined basis (includes all active UMCs) or for individual UMCs.

E.g. measurement across all UMCs

  $ sudo perf stat -e amd_umc/umc_cas_cmd.all/ -a -- sleep 1

   Performance counter stats for 'system wide':

	     544,810      amd_umc/umc_cas_cmd.all/

	 1.002012663 seconds time elapsed

E.g. measurement specific to certain UMCs

  $ sudo perf stat -e amd_umc_0/umc_cas_cmd.all/ -e amd_umc_4/umc_cas_cmd.all/ -a -- sleep 1

   Performance counter stats for 'system wide':

	      27,096      amd_umc_0/umc_cas_cmd.all/
	      35,136      amd_umc_4/umc_cas_cmd.all/

	 1.001602807 seconds time elapsed

The available UMCs can be found from sysfs and the socket to which they
belong can be derived from the cpumask.

E.g.

  $ find /sys/bus/event_source/devices/ -maxdepth 1 -name "amd_umc_*" | sort

  /sys/bus/event_source/devices/amd_umc_0
  /sys/bus/event_source/devices/amd_umc_1
  /sys/bus/event_source/devices/amd_umc_2
  /sys/bus/event_source/devices/amd_umc_3
  /sys/bus/event_source/devices/amd_umc_4
  /sys/bus/event_source/devices/amd_umc_5
  /sys/bus/event_source/devices/amd_umc_6
  /sys/bus/event_source/devices/amd_umc_7

  $ cat /sys/devices/amd_umc_0/cpumask
  0

  $ cat /sys/devices/amd_umc_4/cpumask
  96

All of the output above comes from a dual socket Genoa system having
96 cores and 4 populated memory channels per socket.

Previous versions can be found at:
v1: https://lore.kernel.org/all/cover.1689748843.git.sandipan.das@amd.com/

Changes in v2:
 - Move collection of PMU CPUID info to startup of UNCORE_STARTING.
 - Remove mechanism to read CPUID information using SMP callbacks.
 - Defer PMU registration to startup of UNCORE_ONLINE since this can
   only be done after collection of CPUID information.
 - Remove mechanism to collect and free up unused uncore contexts as
   this is no longer required.
 - Rename some structures (amd_uncore is now called amd_uncore_pmu and
   amd_uncore is instead a collection of amd_uncore_pmu instances).
 - Add new uncore management handlers (scan, init, move, free) which are
   called at different stages of CPU hotplug.
 - Add Acked-by from Ian Rogers for the JSON events.

Sandipan Das (6):
  perf/x86/amd/uncore: Refactor uncore management
  perf/x86/amd/uncore: Move discovery and registration
  perf/x86/amd/uncore: Use rdmsr if rdpmc is unavailable
  perf/x86/amd/uncore: Add group exclusivity
  perf/x86/amd/uncore: Add memory controller support
  perf vendor events amd: Add Zen 4 memory controller events

 arch/x86/events/amd/uncore.c                  | 1036 +++++++++++------
 arch/x86/include/asm/msr-index.h              |    4 +
 arch/x86/include/asm/perf_event.h             |    9 +
 .../arch/x86/amdzen4/memory-controller.json   |  101 ++
 .../arch/x86/amdzen4/recommended.json         |   84 ++
 tools/perf/pmu-events/jevents.py              |    2 +
 6 files changed, 879 insertions(+), 357 deletions(-)
 create mode 100644 tools/perf/pmu-events/arch/x86/amdzen4/memory-controller.json

-- 
2.34.1