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 0/3] Update Alderlake and IcelakeX events
Date: Mon, 27 Feb 2023 18:42:46 -0300 [thread overview]
Message-ID: <Y/0j1qdJdma/TC1B@kernel.org> (raw)
In-Reply-To: <20230223055306.296179-1-irogers@google.com>
Em Wed, Feb 22, 2023 at 09:53:03PM -0800, Ian Rogers escreveu:
> Update Alderlake and IcelakeX events to v1.19.
>
> Developed on the perf-tools-next branch of:
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
Thanks, applied.
- Arnaldo
> Ian Rogers (3):
> perf vendor events intel: Update alderlake to v1.19
> perf vendor events intel: Update alderlaken to v1.19
> perf vendor events intel: Update icelakex to v1.19
>
> .../pmu-events/arch/x86/alderlake/memory.json | 8 +++++
> .../arch/x86/alderlake/pipeline.json | 10 ++++++
> .../arch/x86/alderlaken/memory.json | 7 +++++
> .../pmu-events/arch/x86/icelakex/cache.json | 8 +++++
> .../arch/x86/icelakex/floating-point.json | 31 +++++++++++++++++++
> .../arch/x86/icelakex/pipeline.json | 10 ++++++
> tools/perf/pmu-events/arch/x86/mapfile.csv | 6 ++--
> 7 files changed, 77 insertions(+), 3 deletions(-)
>
> --
> 2.39.2.637.g21b0678d19-goog
>
--
- Arnaldo
prev parent reply other threads:[~2023-02-27 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 5:53 [PATCH v1 0/3] Update Alderlake and IcelakeX events Ian Rogers
2023-02-23 5:53 ` [PATCH v1 1/3] perf vendor events intel: Update alderlake to v1.19 Ian Rogers
2023-02-23 5:53 ` [PATCH v1 2/3] perf vendor events intel: Update alderlaken " Ian Rogers
2023-02-23 5:53 ` [PATCH v1 3/3] perf vendor events intel: Update icelakex " Ian Rogers
2023-02-27 21:42 ` 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=Y/0j1qdJdma/TC1B@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.