From: Ingo Molnar <mingo@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: linux-tip-commits@vger.kernel.org, rene@exactcode.de,
"Borislav Petkov (AMD)" <bp@alien8.de>,
x86@kernel.org, Peter Zijlstra <peterz@infradead.org>
Subject: Re: [tip: x86/urgent] x86/cpu: Fix AMD erratum #1485 on Zen4-based CPUs
Date: Wed, 11 Oct 2023 23:28:26 +0200 [thread overview]
Message-ID: <ZScTem8iF8CUZqf6@gmail.com> (raw)
In-Reply-To: <169701622768.3135.17489375930381616520.tip-bot2@tip-bot2>
* tip-bot2 for Borislav Petkov (AMD) <tip-bot2@linutronix.de> wrote:
> /* AMD Last Branch Record MSRs */
> #define MSR_AMD64_LBR_SELECT 0xc000010e
>
> +/* Zen4 */
> +#define MSR_ZEN4_BP_CFG 0xc001102e
> +#define MSR_ZEN4_BP_CFG_SHARED_BTB_FIX_BIT 5
>
> +/* Zen 2 */
> #define MSR_ZEN2_SPECTRAL_CHICKEN 0xc00110e3
> #define MSR_ZEN2_SPECTRAL_CHICKEN_BIT BIT_ULL(1)
>
> +/* Fam 17h MSRs */
> +#define MSR_F17H_IRPERF 0xc00000e9
Yeah, so these latest AMD MSR definitions in <asm/msr-index.h> are pretty
confused, they list MSRs in the following order:
Zen 4
Zen 2
Fam 19h // resolution in tip:master
Fam 17h
where perf/core added a Fam 19h section a couple of days ago ...
While in reality:
Zen 2 == Fam 17h
Zen 4 == Fam 19h
So it's confusing to list these separately and out of order.
So in resolving the conflict in perf/core I updated this section to read:
/* Fam 19h (Zen 4) MSRs */
#define MSR_F19H_UMC_PERF_CTL 0xc0010800
#define MSR_F19H_UMC_PERF_CTR 0xc0010801
#define MSR_ZEN4_BP_CFG 0xc001102e
#define MSR_ZEN4_BP_CFG_SHARED_BTB_FIX_BIT 5
/* Fam 17h (Zen 2) MSRs */
#define MSR_F17H_IRPERF 0xc00000e9
#define MSR_ZEN2_SPECTRAL_CHICKEN 0xc00110e3
#define MSR_ZEN2_SPECTRAL_CHICKEN_BIT BIT_ULL(1)
This doesn't change the definitions themselves, only merges the comments
and the sections, (to keep the Git conflict resolution non-evil), but
arguably once perf/core goes upstream, we should probably unify the naming
to follow the existing nomenclature, which is, starting at around F15H, the
following:
MSR_F15H_
MSR_F16H_
MSR_F17H_
MSR_F19H_
Or are the MSRs named ZEN2 and ZEN4 in AMD SDMs, which we should follow?
Anyway, something to keep in mind.
Thanks,
Ingo
next prev parent reply other threads:[~2023-10-11 21:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 15:29 [RFC] AMD Zen4 CPU bug? Spurious SMT Sibling Invalid Opcode Speculation René Rebe
2023-10-04 22:25 ` Borislav Petkov
2023-10-06 9:21 ` René Rebe
2023-10-06 9:32 ` Borislav Petkov
2023-10-10 8:39 ` Borislav Petkov
2023-10-10 21:18 ` René Rebe
2023-10-11 8:59 ` Borislav Petkov
2023-10-11 9:23 ` [tip: x86/urgent] x86/cpu: Fix AMD erratum #1485 on Zen4-based CPUs tip-bot2 for Borislav Petkov (AMD)
2023-10-11 21:28 ` Ingo Molnar [this message]
2023-10-12 7:40 ` Borislav Petkov
2023-10-12 18:12 ` [PATCH] x86/cpu: Fix the AMD Fam 17h, Fam 19h, Zen2 and Zen4 enumerations Ingo Molnar
2023-10-12 18:20 ` [tip: perf/core] x86/cpu: Fix the AMD Fam 17h, Fam 19h, Zen2 and Zen4 MSR enumerations tip-bot2 for Borislav Petkov
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=ZScTem8iF8CUZqf6@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rene@exactcode.de \
--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.