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>,
"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>,
"Kan Liang" <kan.liang@linux.intel.com>,
"Andreas Färber" <afaerber@suse.de>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Caleb Biggers" <caleb.biggers@intel.com>,
"Thomas Falcon" <thomas.falcon@intel.com>,
"Weilin Wang" <weilin.wang@intel.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
linux-actions@lists.infradead.org
Subject: Re: [PATCH v2 00/20] Intel TMA 5.1 metrics and event updates
Date: Thu, 4 Sep 2025 18:19:27 -0300 [thread overview]
Message-ID: <aLoCX-hWbTWIGchB@x1> (raw)
In-Reply-To: <20250818190416.145274-1-irogers@google.com>
On Mon, Aug 18, 2025 at 12:03:56PM -0700, Ian Rogers wrote:
> Update events from:
> v1.31 -> v1.33 for alderlake
> v1.09 -> v1.12 for arrowlake
> v1.14 -> v1.16 for emeraldrapids
> v1.10 -> v1.12 for graniterpaids
> v1.14 -> v1.17 for lunarlake
> v1.14 -> v1.16 for meteorlake
> v1.28 -> v1.30 for sapphirerapids
> Update TMA 5.0 to 5.1 removing the slots event workaround as the patch series:
> https://lore.kernel.org/lkml/20250719030517.1990983-1-irogers@google.com/
> is assumed.
Thanks, applied to perf-tools-next,
- Arnaldo
prev parent reply other threads:[~2025-09-04 21:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 19:03 [PATCH v2 00/20] Intel TMA 5.1 metrics and event updates Ian Rogers
2025-08-18 19:03 ` [PATCH v2 01/20] perf parse-events: Handle fake PMUs in CPU terms Ian Rogers
2025-08-18 19:03 ` [PATCH v2 02/20] perf vendor events: Update alderlake events/metrics Ian Rogers
2025-08-18 19:03 ` [PATCH v2 03/20] perf vendor events: Update arrowlake events/metrics Ian Rogers
2025-08-18 19:04 ` [PATCH v2 04/20] perf vendor events: Update broadwell metrics Ian Rogers
2025-08-18 19:04 ` [PATCH v2 05/20] perf vendor events: Update cascadelakex metrics Ian Rogers
2025-08-18 19:04 ` [PATCH v2 06/20] perf vendor events: Update emeraldrapids events/metrics Ian Rogers
2025-08-18 19:04 ` [PATCH v2 07/20] perf vendor events: Update grandridge metrics Ian Rogers
2025-08-18 19:04 ` [PATCH v2 08/20] perf vendor events: Update graniterapids events/metrics Ian Rogers
2025-08-18 19:04 ` [PATCH v2 09/20] perf vendor events: Update haswell metrics Ian Rogers
2025-08-18 19:04 ` [PATCH v2 10/20] perf vendor events: Update icelake metrics Ian Rogers
2025-08-18 19:04 ` [PATCH v2 11/20] perf vendor events: Update ivybridge/ivytown metrics Ian Rogers
2025-08-18 19:04 ` [PATCH v2 12/20] perf vendor events: Update jaketown metrics Ian Rogers
2025-08-18 19:04 ` [PATCH v2 13/20] perf vendor events: Update lunarlake events/metrics Ian Rogers
2025-08-18 19:04 ` [PATCH v2 14/20] perf vendor events: Update meteorlake events/metrics Ian Rogers
2025-08-18 19:04 ` [PATCH v2 15/20] perf vendor events: Update rocketlake metrics Ian Rogers
2025-08-18 19:04 ` [PATCH v2 16/20] perf vendor events: Update sandybridge metrics Ian Rogers
2025-08-18 19:04 ` [PATCH v2 17/20] perf vendor events: Update sapphirerapids events/metrics Ian Rogers
2025-08-18 19:04 ` [PATCH v2 18/20] perf vendor events: Update sierraforest metrics Ian Rogers
2025-08-18 19:04 ` [PATCH v2 19/20] perf vendor events: Update skylake metrics Ian Rogers
2025-08-18 19:04 ` [PATCH v2 20/20] perf vendor events: Update tigerlake metrics Ian Rogers
2025-09-04 16:12 ` [PATCH v2 00/20] Intel TMA 5.1 metrics and event updates Ian Rogers
2025-09-04 21:19 ` 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=aLoCX-hWbTWIGchB@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=afaerber@suse.de \
--cc=alexander.shishkin@linux.intel.com \
--cc=caleb.biggers@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-actions@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=thomas.falcon@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).