From: Greg KH <gregkh@linuxfoundation.org>
To: Mahmoud Adam <mngyadam@amazon.com>
Cc: stable@vger.kernel.org
Subject: Re: backport: perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table
Date: Fri, 15 Dec 2023 18:25:50 +0100 [thread overview]
Message-ID: <2023121545-willing-grew-7edb@gregkh> (raw)
In-Reply-To: <lrkyqil4zh097.fsf@dev-dsk-mngyadam-1c-a2602c62.eu-west-1.amazon.com>
On Fri, Dec 15, 2023 at 05:57:24PM +0100, Mahmoud Adam wrote:
> Hi,
>
> Please backport following commit to 6.1 and 5.15.
>
> Commit 5d515ee40cb57ea5331998f27df7946a69f14dc3 upstream
>
> On SPR MCC the discovery table of UPI is broken, there is a patchset [1]
> to mitigate this which landed around v6.3, this can't be backported to
> stable releases since it is based on SPR related patches which will be
> needed in case of mitigation backport, but already WARN_ON_ONCE in this
> case is not needed here since this is hardware problem that linux can do
> nothing about it, this patch replace WARN_ON_ONCE with pr_info, and
> specify what uncore unit is dropped and the reason
>
> [1] https://lore.kernel.org/all/20230112200105.733466-1-kan.liang@linux.intel.com/
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2023-12-15 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 16:57 backport: perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table Mahmoud Adam
2023-12-15 17:25 ` Greg KH [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=2023121545-willing-grew-7edb@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=mngyadam@amazon.com \
--cc=stable@vger.kernel.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