From: "Liang, Kan" <kan.liang@linux.intel.com>
To: peterz@infradead.org, mingo@redhat.com, linux-kernel@vger.kernel.org
Cc: steve.wahl@hpe.com, alexander.antonov@linux.intel.com,
ak@linux.intel.com, eranian@google.com, namhyung@kernel.org
Subject: Re: [PATCH 0/5] Fix UPI uncore issue on SPR
Date: Wed, 4 Jan 2023 14:57:05 -0500 [thread overview]
Message-ID: <e6445b3e-302e-e25f-ea3c-b6c5dbfdc743@linux.intel.com> (raw)
In-Reply-To: <20221129191023.936738-1-kan.liang@linux.intel.com>
Hi Peter,
Happy new year!
Gentle Ping. Please let me know if you have any comments on the patch set.
Thanks,
Kan
On 2022-11-29 2:10 p.m., kan.liang@linux.intel.com wrote:
> From: Kan Liang <kan.liang@linux.intel.com>
>
> The discovery table of UPI on SPR MCC is broken. The patch series is
> to mitigate the issue by providing a hardcode pre-defined table.
>
> The broken discovery table can trigger a kernel warning message, which
> is overkilled. The patch series also refine the error handling code.
>
> Kan Liang (5):
> perf/x86/uncore: Factor out uncore_device_to_die()
> perf/x86/uncore: Fix potential NULL pointer in uncore_get_alias_name
> perf/x86/uncore: Ignore broken units in discovery table
> perf/x86/uncore: Add a quirk for UPI on SPR
> perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table
>
> arch/x86/events/intel/uncore.c | 34 ++++-
> arch/x86/events/intel/uncore.h | 4 +
> arch/x86/events/intel/uncore_discovery.c | 60 ++++++---
> arch/x86/events/intel/uncore_discovery.h | 14 +-
> arch/x86/events/intel/uncore_snbep.c | 158 ++++++++++++++++++-----
> 5 files changed, 210 insertions(+), 60 deletions(-)
>
prev parent reply other threads:[~2023-01-04 19:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 19:10 [PATCH 0/5] Fix UPI uncore issue on SPR kan.liang
2022-11-29 19:10 ` [PATCH 1/5] perf/x86/uncore: Factor out uncore_device_to_die() kan.liang
2022-11-29 19:10 ` [PATCH 2/5] perf/x86/uncore: Fix potential NULL pointer in uncore_get_alias_name kan.liang
2022-11-29 19:10 ` [PATCH 3/5] perf/x86/uncore: Ignore broken units in discovery table kan.liang
2022-11-29 19:10 ` [PATCH 4/5] perf/x86/uncore: Add a quirk for UPI on SPR kan.liang
2022-11-29 19:10 ` [PATCH 5/5] perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table kan.liang
2023-01-04 19:57 ` 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=e6445b3e-302e-e25f-ea3c-b6c5dbfdc743@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.antonov@linux.intel.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=steve.wahl@hpe.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