public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
	Sandipan Das <sandipan.das@amd.com>,
	x86@kernel.org
Subject: Re: [tip: x86/urgent] x86/cpu/amd: Fix workaround for erratum 1054
Date: Fri, 18 Apr 2025 14:11:44 +0200	[thread overview]
Message-ID: <aAJBgCjGpvyI43E3@gmail.com> (raw)
In-Reply-To: <20250418104013.GAaAIsDW2skB12L-nm@renoirsky.local>


* Borislav Petkov <bp@alien8.de> wrote:

> > Fixes: 232afb557835 ("x86/CPU/AMD: Add X86_FEATURE_ZEN1")
> > Signed-off-by: Sandipan Das <sandipan.das@amd.com>
> > Signed-off-by: Ingo Molnar <mingo@kernel.org>
> > Link: https://lore.kernel.org/r/caa057a9d6f8ad579e2f1abaa71efbd5bd4eaf6d.1744956467.git.sandipan.das@amd.com
> 
> This needs
> 
> Cc: <stable@kernel.org>

No, it doesn't really 'need' a stable tag, it has a Fixes tag already, 
which gets processed by the -stable team.

Also, the bug is old, 1.5 years old:

  Date: Sat, 2 Dec 2023 12:50:23 +0100

plus the erratum is a perf-counters information quality bug affecting 
what appears to be a limited number of models, with the workaround 
likely incorporated in BIOS updates as well. Leave it up to the -stable 
team whether they think it's severe enough to backport it?

Thanks,

	Ingo

  reply	other threads:[~2025-04-18 12:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-18  6:36 [tip: x86/urgent] x86/cpu/amd: Fix workaround for erratum 1054 tip-bot2 for Sandipan Das
2025-04-18 10:40 ` Borislav Petkov
2025-04-18 12:11   ` Ingo Molnar [this message]
2025-04-18 12:32     ` Ingo Molnar
2025-04-18 12:37     ` Borislav Petkov
2025-04-18 12:41       ` Ingo Molnar
2025-04-18 12:47       ` Greg KH
2025-04-18 12:56         ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2025-04-18 12:37 tip-bot2 for Sandipan Das

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=aAJBgCjGpvyI43E3@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=sandipan.das@amd.com \
    --cc=x86@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