From: kan.liang@linux.intel.com
To: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
namhyung@kernel.org, irogers@google.com, adrian.hunter@intel.com,
alexander.shishkin@linux.intel.com, linux-kernel@vger.kernel.org
Cc: ak@linux.intel.com, Kan Liang <kan.liang@linux.intel.com>
Subject: [PATCH 0/4] Support Lunar Lake and Arrow Lake uncore PMU
Date: Thu, 4 Apr 2024 07:17:02 -0700 [thread overview]
Message-ID: <20240404141706.1235531-1-kan.liang@linux.intel.com> (raw)
From: Kan Liang <kan.liang@linux.intel.com>
From the uncore PMU's perspective, the Lunar Lake and Arrow Lake are the
same, which are similar to the previous generation Meteor Lake. The
uncore PerfMon registers are located at both MSR and MMIO space.
The patch set is to enable the uncore PMUs for the Lunar Lake and
Arrow Lake.
Kan Liang (2):
perf/x86/intel/uncore: Factor out common MMIO init and ops functions
perf/x86/intel/uncore: Add Lunar Lake and Arrow Lake support
Zhenyu Wang (2):
perf/x86/intel/uncore: Add LNL uncore iMC freerunning support
perf/x86/intel/uncore: Use D0:F0 as a default device
arch/x86/events/intel/uncore.c | 7 ++
arch/x86/events/intel/uncore.h | 2 +
arch/x86/events/intel/uncore_snb.c | 169 ++++++++++++++++++++++++++---
3 files changed, 161 insertions(+), 17 deletions(-)
--
2.35.1
next reply other threads:[~2024-04-04 14:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 14:17 kan.liang [this message]
2024-04-04 14:17 ` [PATCH 1/4] perf/x86/intel/uncore: Factor out common MMIO init and ops functions kan.liang
2024-04-04 14:17 ` [PATCH 2/4] perf/x86/intel/uncore: Add Lunar Lake and Arrow Lake support kan.liang
2024-04-04 14:17 ` [PATCH 3/4] perf/x86/intel/uncore: Add LNL uncore iMC freerunning support kan.liang
2024-04-04 14:17 ` [PATCH 4/4] perf/x86/intel/uncore: Use D0:F0 as a default device kan.liang
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=20240404141706.1235531-1-kan.liang@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
/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