From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Greg KH <gregkh@linuxfoundation.org>,
stable <stable@vger.kernel.org>,
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:41:25 +0200 [thread overview]
Message-ID: <aAJIdUAHfwo8d7WS@gmail.com> (raw)
In-Reply-To: <20250418123713.GCaAJHedTC_JWN__Td@fat_crate.local>
* Borislav Petkov <bp@alien8.de> wrote:
> > plus the erratum is a perf-counters information quality bug
> > affecting what appears to be a limited number of models, with the
> > workaround
>
> No, the fix is needed because Zen2 and newer won't set
> MSR_K7_HWCR_IRPERF_EN_BIT. It needs to go everywhere.
Fair enough - the current version already has Cc: stable:
263e55949d89 x86/cpu/amd: Fix workaround for erratum 1054
...
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>
Acked-by: Borislav Petkov <bp@alien8.de>
Cc: stable@vger.kernel.org
Link: https://lore.kernel.org/r/caa057a9d6f8ad579e2f1abaa71efbd5bd4eaf6d.1744956467.git.sandipan.das@amd.com
Thanks,
Ingo
next prev parent reply other threads:[~2025-04-18 12:41 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
2025-04-18 12:32 ` Ingo Molnar
2025-04-18 12:37 ` Borislav Petkov
2025-04-18 12:41 ` Ingo Molnar [this message]
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=aAJIdUAHfwo8d7WS@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=sandipan.das@amd.com \
--cc=stable@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.