From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Zhengjun Xing <zhengjun.xing@linux.intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Edward Baker <edward.baker@intel.com>
Subject: Re: [PATCH v1] perf vendor events intel: Update ivybridge and ivytown
Date: Thu, 30 Mar 2023 18:17:43 -0300 [thread overview]
Message-ID: <ZCX8d7ZSUdTGk1Jj@kernel.org> (raw)
In-Reply-To: <20230328234142.1080045-1-irogers@google.com>
Em Tue, Mar 28, 2023 at 04:41:42PM -0700, Ian Rogers escreveu:
> Update to versions 24 and 23 respectively. Adds the event
> BR_MISP_EXEC.INDIRECT.
Thanks, applied.
- Arnaldo
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/perf/pmu-events/arch/x86/ivybridge/pipeline.json | 8 ++++++++
> tools/perf/pmu-events/arch/x86/ivytown/pipeline.json | 8 ++++++++
> tools/perf/pmu-events/arch/x86/mapfile.csv | 4 ++--
> 3 files changed, 18 insertions(+), 2 deletions(-)
>
> diff --git a/tools/perf/pmu-events/arch/x86/ivybridge/pipeline.json b/tools/perf/pmu-events/arch/x86/ivybridge/pipeline.json
> index d1e64e0d683e..30a3da9cd22b 100644
> --- a/tools/perf/pmu-events/arch/x86/ivybridge/pipeline.json
> +++ b/tools/perf/pmu-events/arch/x86/ivybridge/pipeline.json
> @@ -215,6 +215,14 @@
> "SampleAfterValue": "200003",
> "UMask": "0xc4"
> },
> + {
> + "BriefDescription": "Speculative mispredicted indirect branches",
> + "EventCode": "0x89",
> + "EventName": "BR_MISP_EXEC.INDIRECT",
> + "PublicDescription": "Counts speculatively miss-predicted indirect branches at execution time. Counts for indirect near CALL or JMP instructions (RET excluded).",
> + "SampleAfterValue": "200003",
> + "UMask": "0xe4"
> + },
> {
> "BriefDescription": "Not taken speculative and retired mispredicted macro conditional branches",
> "EventCode": "0x89",
> diff --git a/tools/perf/pmu-events/arch/x86/ivytown/pipeline.json b/tools/perf/pmu-events/arch/x86/ivytown/pipeline.json
> index d1e64e0d683e..30a3da9cd22b 100644
> --- a/tools/perf/pmu-events/arch/x86/ivytown/pipeline.json
> +++ b/tools/perf/pmu-events/arch/x86/ivytown/pipeline.json
> @@ -215,6 +215,14 @@
> "SampleAfterValue": "200003",
> "UMask": "0xc4"
> },
> + {
> + "BriefDescription": "Speculative mispredicted indirect branches",
> + "EventCode": "0x89",
> + "EventName": "BR_MISP_EXEC.INDIRECT",
> + "PublicDescription": "Counts speculatively miss-predicted indirect branches at execution time. Counts for indirect near CALL or JMP instructions (RET excluded).",
> + "SampleAfterValue": "200003",
> + "UMask": "0xe4"
> + },
> {
> "BriefDescription": "Not taken speculative and retired mispredicted macro conditional branches",
> "EventCode": "0x89",
> diff --git a/tools/perf/pmu-events/arch/x86/mapfile.csv b/tools/perf/pmu-events/arch/x86/mapfile.csv
> index 41d755d570e6..97b3ffc284a6 100644
> --- a/tools/perf/pmu-events/arch/x86/mapfile.csv
> +++ b/tools/perf/pmu-events/arch/x86/mapfile.csv
> @@ -14,8 +14,8 @@ GenuineIntel-6-(3C|45|46),v33,haswell,core
> GenuineIntel-6-3F,v27,haswellx,core
> GenuineIntel-6-(7D|7E|A7),v1.17,icelake,core
> GenuineIntel-6-6[AC],v1.19,icelakex,core
> -GenuineIntel-6-3A,v23,ivybridge,core
> -GenuineIntel-6-3E,v22,ivytown,core
> +GenuineIntel-6-3A,v24,ivybridge,core
> +GenuineIntel-6-3E,v23,ivytown,core
> GenuineIntel-6-2D,v23,jaketown,core
> GenuineIntel-6-(57|85),v10,knightslanding,core
> GenuineIntel-6-A[AC],v1.01,meteorlake,core
> --
> 2.40.0.348.gf938b09366-goog
>
--
- Arnaldo
prev parent reply other threads:[~2023-03-30 21:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 23:41 [PATCH v1] perf vendor events intel: Update ivybridge and ivytown Ian Rogers
2023-03-30 21:17 ` Arnaldo Carvalho de Melo [this message]
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=ZCX8d7ZSUdTGk1Jj@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=edward.baker@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=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=zhengjun.xing@linux.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).