From: zhengjun.xing@linux.intel.com
To: acme@kernel.org, peterz@infradead.org, mingo@redhat.com,
alexander.shishkin@intel.com, jolsa@kernel.org,
namhyung@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
irogers@google.com, ak@linux.intel.com,
kan.liang@linux.intel.com, zhengjun.xing@linux.intel.com
Subject: [PATCH 01/11] perf vendor events: Update metrics for broadwellde
Date: Fri, 12 Aug 2022 16:52:29 +0800 [thread overview]
Message-ID: <20220812085239.3089231-2-zhengjun.xing@linux.intel.com> (raw)
In-Reply-To: <20220812085239.3089231-1-zhengjun.xing@linux.intel.com>
From: Zhengjun Xing <zhengjun.xing@linux.intel.com>
The metrics are based on TMA 4.4 full, add new metrics “UNCORE_FREQ” for
broadwellde.
Use script at:
https://github.com/intel/event-converter-for-linux-perf/blob/master/download_and_gen.py
to download and generate the latest events and metrics. Manually copy
the broadwellde files into perf.
Signed-off-by: Zhengjun Xing <zhengjun.xing@linux.intel.com>
---
.../perf/pmu-events/arch/x86/broadwellde/bdwde-metrics.json | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/tools/perf/pmu-events/arch/x86/broadwellde/bdwde-metrics.json b/tools/perf/pmu-events/arch/x86/broadwellde/bdwde-metrics.json
index 6789285555f0..b6fdf5ba2c9a 100644
--- a/tools/perf/pmu-events/arch/x86/broadwellde/bdwde-metrics.json
+++ b/tools/perf/pmu-events/arch/x86/broadwellde/bdwde-metrics.json
@@ -450,6 +450,12 @@
"MetricGroup": "SoC",
"MetricName": "Socket_CLKS"
},
+ {
+ "BriefDescription": "Uncore frequency per die [GHZ]",
+ "MetricExpr": "cbox_0@event\\=0x0@ / #num_dies / duration_time / 1000000000",
+ "MetricGroup": "SoC",
+ "MetricName": "UNCORE_FREQ"
+ },
{
"BriefDescription": "Instructions per Far Branch ( Far Branches apply upon transition from application to operating system, handling interrupts, exceptions) [lower number means higher occurrence rate]",
"MetricExpr": "INST_RETIRED.ANY / BR_INST_RETIRED.FAR_BRANCH:u",
--
2.25.1
next prev parent reply other threads:[~2022-08-12 8:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 8:52 [PATCH 00/11] Add generated latest Intel events and metrics zhengjun.xing
2022-08-12 8:52 ` zhengjun.xing [this message]
2022-08-12 8:52 ` [PATCH 02/11] perf vendor events: Update events and metrics for broadwellx zhengjun.xing
2022-08-12 8:52 ` [PATCH 04/11] perf vendor events: Update events and metrics for haswellx zhengjun.xing
2022-08-12 8:52 ` [PATCH 06/11] perf vendor events: Update metrics for ivytown zhengjun.xing
2022-08-12 8:52 ` [PATCH 07/11] perf vendor events: Update metrics for jaketown zhengjun.xing
2022-08-12 8:52 ` [PATCH 08/11] perf vendor events: Update events for knightslanding zhengjun.xing
2022-08-12 8:52 ` [PATCH 09/11] perf vendor events: Update metrics for sapphirerapids zhengjun.xing
2022-08-12 8:52 ` [PATCH 11/11] perf vendor events: Update events for snowridgex zhengjun.xing
[not found] ` <CAP-5=fVTOvY0_3PxrzP28iFn0FtDgQE34qJ4_6+fD-TQohCFQQ@mail.gmail.com>
2022-08-13 16:52 ` [PATCH 00/11] Add generated latest Intel events and metrics Xing Zhengjun
2022-08-13 18:08 ` Arnaldo Carvalho de Melo
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=20220812085239.3089231-2-zhengjun.xing@linux.intel.com \
--to=zhengjun.xing@linux.intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@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;
as well as URLs for NNTP newsgroup(s).