From: Ingo Molnar <mingo@kernel.org>
To: "Liang, Kan" <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] perf/x86/uncore: Correct the number of CHAs on EMR
Date: Mon, 4 Sep 2023 21:10:05 +0200 [thread overview]
Message-ID: <ZPYrjW9+hIOJODHY@gmail.com> (raw)
In-Reply-To: <37afe50a-44f1-7fb1-c4c0-1e45c38c9a6d@linux.intel.com>
* Liang, Kan <kan.liang@linux.intel.com> wrote:
>
>
> On 2023-09-03 4:40 a.m., Ingo Molnar wrote:
> >
> > * kan.liang@linux.intel.com <kan.liang@linux.intel.com> wrote:
> >
> >> From: Kan Liang <kan.liang@linux.intel.com>
> >>
> >> The MSR UNC_CBO_CONFIG, which was used to detect the number of CHAs on
> >> SPR, is broken on EMR XCC. It always returns 0.
> >>
> >> Roll back to the discovery method, which can give the correct number for
> >> this case.
> >>
> >> 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 | 4 +++-
> >> 1 file changed, 3 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/arch/x86/events/intel/uncore_snbep.c b/arch/x86/events/intel/uncore_snbep.c
> >> index d49e90dc04a4..c41d7d46481c 100644
> >> --- a/arch/x86/events/intel/uncore_snbep.c
> >> +++ b/arch/x86/events/intel/uncore_snbep.c
> >> @@ -6475,7 +6475,9 @@ void spr_uncore_cpu_init(void)
> >> type = uncore_find_type_by_id(uncore_msr_uncores, UNCORE_SPR_CHA);
> >> if (type) {
> >> rdmsrl(SPR_MSR_UNC_CBO_CONFIG, num_cbo);
> >> - type->num_boxes = num_cbo;
> >> + /* The MSR doesn't work on the EMR XCC. Roll back to the discovery method. */
> >> + if (num_cbo)
> >> + type->num_boxes = num_cbo;
> >
> > So in the zero case we don't write type->num_boxes and leave it as-is.
> >
> > How does this fall back to the discovery method, is the existing (default?)
> > value of type->num_boxes some special value?
> >
>
> Starts from SPR, the basic uncore PMON information are 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
> SPR_MSR_UNC_CBO_CONFIG to replace the one from the discovery table.
> 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 (It works well for other EMR variants). But the above firmware bug
> doesn't impact the EMR XCC. So this patch NOT lets the value from the
> SPR_MSR_UNC_CBO_CONFIG replace the existing value from the discovery table.
Thanks - the comment & changelog should probably reflect this background.
Ingo
next prev parent reply other threads:[~2023-09-04 19:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 14:20 [PATCH] perf/x86/uncore: Correct the number of CHAs on EMR kan.liang
2023-09-03 8:40 ` Ingo Molnar
2023-09-04 15:37 ` Liang, Kan
2023-09-04 19:10 ` Ingo Molnar [this message]
2023-09-05 13:22 ` Liang, Kan
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=ZPYrjW9+hIOJODHY@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