From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Ian Rogers <irogers@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Perry Taylor <perry.taylor@intel.com>,
Samantha Alt <samantha.alt@intel.com>,
Caleb Biggers <caleb.biggers@intel.com>,
Weilin Wang <weilin.wang@intel.com>,
Edward Baker <edward.baker@intel.com>
Subject: Re: [PATCH v4 07/22] perf jevents: Add br metric group for branch statistics on Intel
Date: Thu, 7 Nov 2024 09:35:32 -0500 [thread overview]
Message-ID: <20a6d424-c3a5-4fa9-b5d4-bcbe684a4a6f@linux.intel.com> (raw)
In-Reply-To: <20240926175035.408668-8-irogers@google.com>
On 2024-09-26 1:50 p.m., Ian Rogers wrote:
> The br metric group for branches itself comprises metric groups for
> total, taken, conditional, fused and far metric groups using json
> events. Conditional taken and not taken metrics are specific to
> Icelake and later generations, so the presence of the event is used to
> determine whether the metric should exist.
> > Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/perf/pmu-events/intel_metrics.py | 138 +++++++++++++++++++++++++
> 1 file changed, 138 insertions(+)
>
> diff --git a/tools/perf/pmu-events/intel_metrics.py b/tools/perf/pmu-events/intel_metrics.py
> index 58e243695f0a..09f7b7159e7c 100755
> --- a/tools/perf/pmu-events/intel_metrics.py
> +++ b/tools/perf/pmu-events/intel_metrics.py
> @@ -123,6 +123,143 @@ def Tsx() -> Optional[MetricGroup]:
> ], description="Breakdown of transactional memory statistics")
>
>
> +def IntelBr():
> + ins = Event("instructions")
> +
> + def Total() -> MetricGroup:
> + br_all = Event ("BR_INST_RETIRED.ALL_BRANCHES", "BR_INST_RETIRED.ANY")
> + br_m_all = Event("BR_MISP_RETIRED.ALL_BRANCHES",
> + "BR_INST_RETIRED.MISPRED",
> + "BR_MISP_EXEC.ANY")
> + br_clr = None
> + try:
> + br_clr = Event("BACLEARS.ANY", "BACLEARS.ALL")
> + except:
> + pass
There is no guarantee to the event name. It could be changed later.
The renaming already occurred several times, even for architectural events.
I think we should test all events' presence, not just a few of them.
There could be some effort in the future to sync with the event list for
each new generation and check if there is a renaming.
Thanks,
Kan
> +
> + br_r = d_ratio(br_all, interval_sec)
> + ins_r = d_ratio(ins, br_all)
> + misp_r = d_ratio(br_m_all, br_all)
> + clr_r = d_ratio(br_clr, interval_sec) if br_clr else None
> +
> + return MetricGroup("br_total", [
> + Metric("br_total_retired",
> + "The number of branch instructions retired per second.", br_r,
> + "insn/s"),
> + Metric(
> + "br_total_mispred",
> + "The number of branch instructions retired, of any type, that were "
> + "not correctly predicted as a percentage of all branch instrucions.",
> + misp_r, "100%"),
> + Metric("br_total_insn_between_branches",
> + "The number of instructions divided by the number of branches.",
> + ins_r, "insn"),
> + Metric("br_total_insn_fe_resteers",
> + "The number of resync branches per second.", clr_r, "req/s"
> + ) if clr_r else None
> + ])
> +
> + def Taken() -> MetricGroup:
> + br_all = Event("BR_INST_RETIRED.ALL_BRANCHES", "BR_INST_RETIRED.ANY")
> + br_m_tk = None
> + try:
> + br_m_tk = Event("BR_MISP_RETIRED.NEAR_TAKEN",
> + "BR_MISP_RETIRED.TAKEN_JCC",
> + "BR_INST_RETIRED.MISPRED_TAKEN")
> + except:
> + pass
> + br_r = d_ratio(br_all, interval_sec)
> + ins_r = d_ratio(ins, br_all)
> + misp_r = d_ratio(br_m_tk, br_all) if br_m_tk else None
> + return MetricGroup("br_taken", [
> + Metric("br_taken_retired",
> + "The number of taken branches that were retired per second.",
> + br_r, "insn/s"),
> + Metric(
> + "br_taken_mispred",
> + "The number of retired taken branch instructions that were "
> + "mispredicted as a percentage of all taken branches.", misp_r,
> + "100%") if misp_r else None,
> + Metric(
> + "br_taken_insn_between_branches",
> + "The number of instructions divided by the number of taken branches.",
> + ins_r, "insn"),
> + ])
> +
> + def Conditional() -> Optional[MetricGroup]:
> + try:
> + br_cond = Event("BR_INST_RETIRED.COND",
> + "BR_INST_RETIRED.CONDITIONAL",
> + "BR_INST_RETIRED.TAKEN_JCC")
> + br_m_cond = Event("BR_MISP_RETIRED.COND",
> + "BR_MISP_RETIRED.CONDITIONAL",
> + "BR_MISP_RETIRED.TAKEN_JCC")
> + except:
> + return None
> +
> + br_cond_nt = None
> + br_m_cond_nt = None
> + try:
> + br_cond_nt = Event("BR_INST_RETIRED.COND_NTAKEN")
> + br_m_cond_nt = Event("BR_MISP_RETIRED.COND_NTAKEN")
> + except:
> + pass
> + br_r = d_ratio(br_cond, interval_sec)
> + ins_r = d_ratio(ins, br_cond)
> + misp_r = d_ratio(br_m_cond, br_cond)
> + taken_metrics = [
> + Metric("br_cond_retired", "Retired conditional branch instructions.",
> + br_r, "insn/s"),
> + Metric("br_cond_insn_between_branches",
> + "The number of instructions divided by the number of conditional "
> + "branches.", ins_r, "insn"),
> + Metric("br_cond_mispred",
> + "Retired conditional branch instructions mispredicted as a "
> + "percentage of all conditional branches.", misp_r, "100%"),
> + ]
> + if not br_m_cond_nt:
> + return MetricGroup("br_cond", taken_metrics)
> +
> + br_r = d_ratio(br_cond_nt, interval_sec)
> + ins_r = d_ratio(ins, br_cond_nt)
> + misp_r = d_ratio(br_m_cond_nt, br_cond_nt)
> +
> + not_taken_metrics = [
> + Metric("br_cond_retired", "Retired conditional not taken branch instructions.",
> + br_r, "insn/s"),
> + Metric("br_cond_insn_between_branches",
> + "The number of instructions divided by the number of not taken conditional "
> + "branches.", ins_r, "insn"),
> + Metric("br_cond_mispred",
> + "Retired not taken conditional branch instructions mispredicted as a "
> + "percentage of all not taken conditional branches.", misp_r, "100%"),
> + ]
> + return MetricGroup("br_cond", [
> + MetricGroup("br_cond_nt", not_taken_metrics),
> + MetricGroup("br_cond_tkn", taken_metrics),
> + ])
> +
> + def Far() -> Optional[MetricGroup]:
> + try:
> + br_far = Event("BR_INST_RETIRED.FAR_BRANCH")
> + except:
> + return None
> +
> + br_r = d_ratio(br_far, interval_sec)
> + ins_r = d_ratio(ins, br_far)
> + return MetricGroup("br_far", [
> + Metric("br_far_retired", "Retired far control transfers per second.",
> + br_r, "insn/s"),
> + Metric(
> + "br_far_insn_between_branches",
> + "The number of instructions divided by the number of far branches.",
> + ins_r, "insn"),
> + ])
> +
> + return MetricGroup("br", [Total(), Taken(), Conditional(), Far()],
> + description="breakdown of retired branch instructions")
> +
> +
> def main() -> None:
> global _args
>
> @@ -150,6 +287,7 @@ def main() -> None:
> Rapl(),
> Smi(),
> Tsx(),
> + IntelBr(),
> ])
>
>
next prev parent reply other threads:[~2024-11-07 14:35 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 17:50 [PATCH v4 00/22] Python generated Intel metrics Ian Rogers
2024-09-26 17:50 ` [PATCH v4 01/22] perf jevents: Add RAPL metrics for all Intel models Ian Rogers
2024-09-26 17:50 ` [PATCH v4 02/22] perf jevents: Add idle metric for " Ian Rogers
2024-11-06 17:01 ` Liang, Kan
2024-11-06 17:08 ` Liang, Kan
2024-09-26 17:50 ` [PATCH v4 03/22] perf jevents: Add smi metric group " Ian Rogers
2024-11-06 17:32 ` Liang, Kan
2024-11-06 17:42 ` Ian Rogers
2024-11-06 18:29 ` Liang, Kan
2024-09-26 17:50 ` [PATCH v4 04/22] perf jevents: Add CheckPmu to see if a PMU is in loaded json events Ian Rogers
2024-09-26 17:50 ` [PATCH v4 05/22] perf jevents: Mark metrics with experimental events as experimental Ian Rogers
2024-09-26 17:50 ` [PATCH v4 06/22] perf jevents: Add tsx metric group for Intel models Ian Rogers
2024-11-06 17:52 ` Liang, Kan
2024-11-06 18:15 ` Ian Rogers
2024-11-06 18:48 ` Liang, Kan
2024-09-26 17:50 ` [PATCH v4 07/22] perf jevents: Add br metric group for branch statistics on Intel Ian Rogers
2024-11-07 14:35 ` Liang, Kan [this message]
2024-11-07 17:19 ` Ian Rogers
2024-09-26 17:50 ` [PATCH v4 08/22] perf jevents: Add software prefetch (swpf) metric group for Intel Ian Rogers
2024-09-26 17:50 ` [PATCH v4 09/22] perf jevents: Add ports metric group giving utilization on Intel Ian Rogers
2024-11-07 15:00 ` Liang, Kan
2024-11-07 17:12 ` Ian Rogers
2024-11-07 19:36 ` Liang, Kan
2024-11-07 21:00 ` Ian Rogers
2024-11-08 16:45 ` Liang, Kan
2024-09-26 17:50 ` [PATCH v4 10/22] perf jevents: Add L2 metrics for Intel Ian Rogers
2024-09-26 17:50 ` [PATCH v4 11/22] perf jevents: Add load store breakdown metrics ldst " Ian Rogers
2024-09-26 17:50 ` [PATCH v4 12/22] perf jevents: Add ILP metrics " Ian Rogers
2024-09-26 17:50 ` [PATCH v4 13/22] perf jevents: Add context switch " Ian Rogers
2024-09-26 17:50 ` [PATCH v4 14/22] perf jevents: Add FPU " Ian Rogers
2024-09-26 17:50 ` [PATCH v4 15/22] perf jevents: Add Miss Level Parallelism (MLP) metric " Ian Rogers
2024-09-26 17:50 ` [PATCH v4 16/22] perf jevents: Add mem_bw " Ian Rogers
2024-09-26 17:50 ` [PATCH v4 17/22] perf jevents: Add local/remote "mem" breakdown metrics " Ian Rogers
2024-09-26 17:50 ` [PATCH v4 18/22] perf jevents: Add dir " Ian Rogers
2024-09-26 17:50 ` [PATCH v4 19/22] perf jevents: Add C-State metrics from the PCU PMU " Ian Rogers
2024-09-26 17:50 ` [PATCH v4 20/22] perf jevents: Add local/remote miss latency metrics " Ian Rogers
2024-09-26 17:50 ` [PATCH v4 21/22] perf jevents: Add upi_bw metric " Ian Rogers
2024-09-26 17:50 ` [PATCH v4 22/22] perf jevents: Add mesh bandwidth saturation " Ian Rogers
2024-09-27 18:33 ` [PATCH v4 00/22] Python generated Intel metrics Liang, Kan
2024-10-09 16:02 ` Ian Rogers
2024-11-06 16:46 ` Liang, Kan
2024-11-13 23:40 ` Ian Rogers
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=20a6d424-c3a5-4fa9-b5d4-bcbe684a4a6f@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=caleb.biggers@intel.com \
--cc=edward.baker@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=perry.taylor@intel.com \
--cc=peterz@infradead.org \
--cc=samantha.alt@intel.com \
--cc=weilin.wang@intel.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;
as well as URLs for NNTP newsgroup(s).