mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Chen, Zide" <zide.chen@intel.com>
To: Peter Zijlstra <peterz@infradead.org>,
	"Mi, Dapeng" <dapeng1.mi@linux.intel.com>
Cc: Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Andi Kleen <ak@linux.intel.com>,
	Eranian Stephane <eranian@google.com>,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH V2 7/7] perf/x86/intel/uncore: Implement global init callback for GNR uncore
Date: Fri, 29 May 2026 10:03:31 -0500	[thread overview]
Message-ID: <882972ce-2c2c-49ad-b2ec-f1c20cc3ff70@intel.com> (raw)
In-Reply-To: <20260529105537.GG3493090@noisy.programming.kicks-ass.net>



On 5/29/2026 5:55 AM, Peter Zijlstra wrote:
> On Fri, May 29, 2026 at 04:47:39PM +0800, Mi, Dapeng wrote:
>>
>> On 5/29/2026 2:14 AM, Chen, Zide wrote:
>>>
>>> On 5/28/2026 1:46 AM, Mi, Dapeng wrote:
>>>> On 5/27/2026 11:11 PM, Zide Chen wrote:
>>>>> On Sierra Forest and Clearwater Forest, the FRZ_ALL bit in the global
>>>>> control register defaults to 0 at boot, but UBOX PMON units do not
>>>>> work until the global control register is explicitly written with 0
>>>>> to trigger hardware initialization properly.
>>>>>
>>>>> Implement the generic uncore_msr_global_init() callback and add it to
>>>>> gnr_uncore_init[], which is shared by GNR, GRR, SRF, and CWF.
>>>> Need a "Fixes" tag?
>>> No Fixes tag needed. This is a hardware initialization workaround rather
>>> than a fix for a software bug. The register defaults to 0, but the
>>> hardware requires an explicit write to trigger PMON functionality.
>>
>> Zide, per my understanding, some uncore PMUs can't work for SRF and CWF
>> without this change. Is it right? If so, we need to add a "Fixes" tag to
>> ensure this patch is merged to the corresponding stable branches. Thanks.
> 
> If you all agree on Fixes tags, then those patches that end up getting
> one should be at the front of the series.
> 
> I was about to pick this up, but if you guys want to send a new series,
> let me know and I'll hold off.

Yes, please hold off and I can send out a new series to add a Fixes tag,
fix the missing '---' in patch 5/7, etc.


  reply	other threads:[~2026-05-29 15:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-27 15:11 [PATCH V2 1/7] perf/x86/intel/uncore: Fix discovery unit lookup for multi-die systems Zide Chen
2026-05-27 15:11 ` [PATCH V2 2/7] perf/x86/intel/uncore: Guard against invalid box control address Zide Chen
2026-05-28  6:03   ` Mi, Dapeng
2026-05-27 15:11 ` [PATCH V2 3/7] perf/x86/intel/uncore: Fix PCI device refcount leak in UPI discovery Zide Chen
2026-05-28  6:34   ` Mi, Dapeng
2026-05-27 15:11 ` [PATCH V2 4/7] perf/x86/intel/uncore: Defer ADL global PMON enable to enable_box() Zide Chen
2026-05-28  6:35   ` Mi, Dapeng
2026-05-28 18:07     ` Chen, Zide
2026-05-27 15:11 ` [PATCH V2 5/7] perf/x86/intel/uncore: Move die_to_cpu() to uncore.c Zide Chen
2026-05-28  6:36   ` Mi, Dapeng
2026-05-29 10:54   ` Peter Zijlstra
2026-05-27 15:11 ` [PATCH V2 6/7] perf/x86/intel/uncore: Fix uncore_die_to_cpu() for offline dies Zide Chen
2026-05-28  6:38   ` Mi, Dapeng
2026-05-27 15:11 ` [PATCH V2 7/7] perf/x86/intel/uncore: Implement global init callback for GNR uncore Zide Chen
2026-05-28  6:46   ` Mi, Dapeng
2026-05-28 18:14     ` Chen, Zide
2026-05-29  8:47       ` Mi, Dapeng
2026-05-29 10:55         ` Peter Zijlstra
2026-05-29 15:03           ` Chen, Zide [this message]
2026-05-28  6:01 ` [PATCH V2 1/7] perf/x86/intel/uncore: Fix discovery unit lookup for multi-die systems Mi, Dapeng

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=882972ce-2c2c-49ad-b2ec-f1c20cc3ff70@intel.com \
    --to=zide.chen@intel.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=dapeng1.mi@linux.intel.com \
    --cc=eranian@google.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

all inboxes | Powered by JetHome®