From: Namhyung Kim <namhyung@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@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>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Ian Rogers <irogers@google.com>
Cc: Weilin Wang <weilin.wang@intel.com>,
Caleb Biggers <caleb.biggers@intel.com>
Subject: Re: [PATCH v2 00/37] Update Intel perf vendor events
Date: Fri, 21 Jun 2024 07:35:57 -0700 [thread overview]
Message-ID: <171898054728.3878341.620083012448507466.b4-ty@kernel.org> (raw)
In-Reply-To: <20240620181752.3945845-1-irogers@google.com>
On Thu, 20 Jun 2024 11:17:14 -0700, Ian Rogers wrote:
> Update Intel perf vendor events from:
> https://github.com/intel/perfmon
> Adds new events and updates TMA metrics to v4.8.
> Add counter and experimental event tags.
>
> Co-authored-by: Weilin Wang <weilin.wang@intel.com>
> Co-authored-by: Caleb Biggers <caleb.biggers@intel.com>
>
> [...]
Applied to perf-tools-next, thanks!
Best regards,
Namhyung
prev parent reply other threads:[~2024-06-21 14:35 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 18:17 Ian Rogers
2024-06-20 18:17 ` [PATCH v2 01/37] perf vendor events: Update alderlake events/metrics Ian Rogers
2024-06-20 18:17 ` [PATCH v2 02/37] perf vendor events: Update alderlaken events/metrics Ian Rogers
2024-06-20 18:17 ` [PATCH v2 03/37] perf vendor events: Add bonnell counter information Ian Rogers
2024-06-20 18:17 ` [PATCH v2 04/37] perf vendor events: Update broadwell metrics add event " Ian Rogers
2024-06-20 18:17 ` [PATCH v2 05/37] perf vendor events: Update broadwellde " Ian Rogers
2024-06-20 18:17 ` [PATCH v2 06/37] perf vendor events: Update broadwellx " Ian Rogers
2024-06-20 18:17 ` [PATCH v2 07/37] perf vendor events: Update cascadelakex events/metrics Ian Rogers
2024-06-20 18:17 ` [PATCH v2 08/37] perf vendor events: Update elkhartlake events Ian Rogers
2024-06-20 18:17 ` [PATCH v2 09/37] perf vendor events: Add/update emeraldrapids events/metrics Ian Rogers
2024-06-20 18:17 ` [PATCH v2 10/37] perf vendor events: Add goldmont counter information Ian Rogers
2024-06-20 18:17 ` [PATCH v2 11/37] perf vendor events: Add goldmontplus " Ian Rogers
2024-06-20 18:17 ` [PATCH v2 12/37] perf vendor events: Update/add grandridge events/metrics Ian Rogers
2024-06-20 18:17 ` [PATCH v2 13/37] perf vendor events: Update graniterapids events and add counter information Ian Rogers
2024-06-20 18:17 ` [PATCH v2 14/37] perf vendor events: Add haswell " Ian Rogers
2024-06-20 18:17 ` [PATCH v2 15/37] perf vendor events: Update haswellx metrics add event " Ian Rogers
2024-06-20 18:17 ` [PATCH v2 16/37] perf vendor events: Add/update icelake events/metrics Ian Rogers
2024-06-20 18:17 ` [PATCH v2 17/37] perf vendor events: Add/update icelakex events/metrics Ian Rogers
2024-06-20 18:17 ` [PATCH v2 18/37] perf vendor events: Update ivybridge metrics add event counter information Ian Rogers
2024-06-20 18:17 ` [PATCH v2 19/37] perf vendor events: Update ivytown " Ian Rogers
2024-06-20 18:17 ` [PATCH v2 20/37] perf vendor events: Update jaketown " Ian Rogers
2024-06-20 18:17 ` [PATCH v2 21/37] perf vendor events: Add knightslanding " Ian Rogers
2024-06-20 18:17 ` [PATCH v2 22/37] perf vendor events: Add lunarlake " Ian Rogers
2024-06-20 18:17 ` [PATCH v2 23/37] perf vendor events: Update meteorlake events and add " Ian Rogers
2024-06-20 18:17 ` [PATCH v2 24/37] perf vendor events: Add nehalemep " Ian Rogers
2024-06-20 18:17 ` [PATCH v2 25/37] perf vendor events: Add nehalemex " Ian Rogers
2024-06-20 18:17 ` [PATCH v2 26/37] perf vendor events: Add/update rocketlake events/metrics Ian Rogers
2024-06-20 18:17 ` [PATCH v2 27/37] perf vendor events: Update sandybridge metrics add event counter information Ian Rogers
2024-06-20 18:17 ` [PATCH v2 28/37] perf vendor events: Add/update sapphirerapids events/metrics Ian Rogers
2024-06-20 18:17 ` [PATCH v2 29/37] perf vendor events: Add/update sierraforest events/metrics Ian Rogers
2024-06-20 18:17 ` [PATCH v2 30/37] perf vendor events: Add silvermont counter information Ian Rogers
2024-06-20 18:17 ` [PATCH v2 31/37] perf vendor events: Add/update skylake events/metrics Ian Rogers
2024-06-20 18:17 ` [PATCH v2 32/37] perf vendor events: Add/update skylakex events/metrics Ian Rogers
2024-06-20 18:17 ` [PATCH v2 33/37] perf vendor events: Add snowridgex counter information Ian Rogers
2024-06-20 18:17 ` [PATCH v2 34/37] perf vendor events: Add/update tigerlake events/metrics Ian Rogers
2024-06-20 18:17 ` [PATCH v2 35/37] perf vendor events: Add westmereep-dp counter information Ian Rogers
2024-06-20 18:17 ` [PATCH v2 36/37] perf vendor events: Add westmereep-sp " Ian Rogers
2024-06-20 18:17 ` [PATCH v2 37/37] perf vendor events: Add westmereex " Ian Rogers
2024-06-21 14:35 ` Namhyung Kim [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=171898054728.3878341.620083012448507466.b4-ty@kernel.org \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexandre.torgue@foss.st.com \
--cc=caleb.biggers@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=mcoquelin.stm32@gmail.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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
all inboxes | Powered by JetHome®