public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: kan.liang@linux.intel.com
Cc: peterz@infradead.org, mingo@redhat.com,
	linux-kernel@vger.kernel.org,
	Stephane Eranian <eranian@google.com>,
	Yunying Sun <yunying.sun@intel.com>
Subject: Re: [PATCH V2] perf/x86/uncore: Correct the number of CHAs on EMR
Date: Tue, 5 Sep 2023 21:51:20 +0200	[thread overview]
Message-ID: <ZPeGuCJ9xWF+EGHY@gmail.com> (raw)
In-Reply-To: <20230905134248.496114-1-kan.liang@linux.intel.com>


* kan.liang@linux.intel.com <kan.liang@linux.intel.com> wrote:

> From: Kan Liang <kan.liang@linux.intel.com>
> 
> Starting from SPR, the basic uncore PMON information is retrieved from
> the discovery table (resides in an MMIO space populated by BIOS). It is
> called the discovery method. The existing value of the type->num_boxes
> is from the discovery table.
> 
> On some SPR variants, there is a firmware bug. So the value from the
> discovery table is incorrect. We use the value from the
> SPR_MSR_UNC_CBO_CONFIG to replace the one from the discovery table.
> Commit 38776cc45eb7 ("perf/x86/uncore: Correct the number of CHAs on SPR")
> 
> Unfortunately, the SPR_MSR_UNC_CBO_CONFIG isn't available for the EMR
> XCC (Always returns 0). But the above firmware bug
> doesn't impact the EMR XCC. Don't let the value from the MSR replace
> the existing value from the discovery table.
> 
> Fixes: 38776cc45eb7 ("perf/x86/uncore: Correct the number of CHAs on SPR")
> Reported-by: Stephane Eranian <eranian@google.com>
> Reported-by: Yunying Sun <yunying.sun@intel.com>
> Tested-by: Yunying Sun <yunying.sun@intel.com>
> Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
> ---
>  arch/x86/events/intel/uncore_snbep.c | 12 +++++++++++-
>  1 file changed, 11 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/x86/events/intel/uncore_snbep.c b/arch/x86/events/intel/uncore_snbep.c
> index 4d349986f76a..8250f0f59c2b 100644
> --- a/arch/x86/events/intel/uncore_snbep.c
> +++ b/arch/x86/events/intel/uncore_snbep.c
> @@ -6474,8 +6474,18 @@ void spr_uncore_cpu_init(void)
>  
>  	type = uncore_find_type_by_id(uncore_msr_uncores, UNCORE_SPR_CHA);
>  	if (type) {
> +		/*
> +		 * The value from the discovery table (stored in the type->num_boxes
> +		 * of UNCORE_SPR_CHA) is incorrect on some SPR variants because of a
> +		 * firmware bug. Using the value from SPR_MSR_UNC_CBO_CONFIG to replace it.
> +		 */
>  		rdmsrl(SPR_MSR_UNC_CBO_CONFIG, num_cbo);
> -		type->num_boxes = num_cbo;
> +		/*
> +		 * The MSR doesn't work on the EMR XCC, but the firmware bug doesn't impact
> +		 * the EMR XCC. Don't let the value from the MSR replace the existing value.
> +		 */
> +		if (num_cbo)
> +			type->num_boxes = num_cbo;

Thank you, that's a perfect description of the quirk - applied to 
tip:perf/urgent.

	Ingo

  reply	other threads:[~2023-09-05 19:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-05 13:42 [PATCH V2] perf/x86/uncore: Correct the number of CHAs on EMR kan.liang
2023-09-05 19:51 ` Ingo Molnar [this message]
2023-09-05 19:54 ` [tip: perf/urgent] " tip-bot2 for 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=ZPeGuCJ9xWF+EGHY@gmail.com \
    --to=mingo@kernel.org \
    --cc=eranian@google.com \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=yunying.sun@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