linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Liang, Kan" <kan.liang@linux.intel.com>
To: "Mi, Dapeng" <dapeng1.mi@linux.intel.com>,
	peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
	namhyung@kernel.org, irogers@google.com,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH V3 0/4] perf: Support Panther Lake uncore
Date: Mon, 7 Jul 2025 13:09:36 -0700	[thread overview]
Message-ID: <6e0c8d1e-a4ed-4b65-a3f0-8801db53e5f1@linux.intel.com> (raw)
In-Reply-To: <b77f58ac-17ac-4397-b1de-d6a8ac9793c3@linux.intel.com>



On 2025-07-03 6:24 p.m., Mi, Dapeng wrote:
> 
> On 7/4/2025 12:56 AM, kan.liang@linux.intel.com wrote:
>> From: Kan Liang <kan.liang@linux.intel.com>
>>
>> Changes since V2:
>> - Rebase on the later tip.git
>>   rdmsrl_safe_on_cpu -> rdmsrq_safe_on_cpu
>>
>> Starting from the Panther Lake, the uncore discovery table mechanism is
>> also introduced into the client platforms. The difference is that the
>> portal of the global discovery table is retrieved from an MSR, rather
>> than MMIO space.
>>
>> The first two patches provide a generic support for the extension of the
>> uncore discovery table mechanism.
>> The rest patches enable the uncore PMU on Panther Lake.
>>
>> Kan Liang (4):
>>   perf/x86/intel/uncore: Support MSR portal for discovery tables
>>   perf/x86/intel/uncore: Support customized MMIO map size
>>   perf/x86/intel/uncore: Add Panther Lake support
>>   perf/x86/intel/uncore: Add iMC freerunning for Panther Lake
>>
>>  arch/x86/events/intel/uncore.c           |  7 ++
>>  arch/x86/events/intel/uncore.h           |  2 +
>>  arch/x86/events/intel/uncore_discovery.c | 89 ++++++++++++++++++------
>>  arch/x86/events/intel/uncore_discovery.h |  7 ++
>>  arch/x86/events/intel/uncore_snb.c       | 79 +++++++++++++++++++++
>>  arch/x86/events/intel/uncore_snbep.c     |  4 +-
>>  6 files changed, 166 insertions(+), 22 deletions(-)
> 
> The whole series looks good to me. Thanks.
> 

Thanks. I will add a reviewed-by tag from you in V4.

Thanks,
Kan


      reply	other threads:[~2025-07-07 20:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-03 16:56 [PATCH V3 0/4] perf: Support Panther Lake uncore kan.liang
2025-07-03 16:56 ` [PATCH V3 1/4] perf/x86/intel/uncore: Support MSR portal for discovery tables kan.liang
2025-07-04  1:04   ` Mi, Dapeng
2025-07-07 20:08     ` Liang, Kan
2025-07-03 16:56 ` [PATCH V3 2/4] perf/x86/intel/uncore: Support customized MMIO map size kan.liang
2025-07-03 16:56 ` [PATCH V3 3/4] perf/x86/intel/uncore: Add Panther Lake support kan.liang
2025-07-03 16:56 ` [PATCH V3 4/4] perf/x86/intel/uncore: Add iMC freerunning for Panther Lake kan.liang
2025-07-04  1:24 ` [PATCH V3 0/4] perf: Support Panther Lake uncore Mi, Dapeng
2025-07-07 20:09   ` Liang, Kan [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=6e0c8d1e-a4ed-4b65-a3f0-8801db53e5f1@linux.intel.com \
    --to=kan.liang@linux.intel.com \
    --cc=acme@kernel.org \
    --cc=dapeng1.mi@linux.intel.com \
    --cc=irogers@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@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;
as well as URLs for NNTP newsgroup(s).