mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yazen Ghannam <yazen.ghannam@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: x86@kernel.org, Tony Luck <tony.luck@intel.com>,
	linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/mce: Use ZENx features for Zen IF quirk
Date: Tue, 12 Aug 2025 10:56:38 -0400	[thread overview]
Message-ID: <20250812145638.GA383670@yaz-khff2.amd.com> (raw)
In-Reply-To: <20250811205529.GBaJpYwcmMfEFqEicm@fat_crate.local>

On Mon, Aug 11, 2025 at 10:55:29PM +0200, Borislav Petkov wrote:
> On Mon, Aug 11, 2025 at 04:34:08PM -0400, Yazen Ghannam wrote:
> > diff --git a/arch/x86/kernel/cpu/mce/core.c b/arch/x86/kernel/cpu/mce/core.c
> > index 4da4eab56c81..0ef164568077 100644
> > --- a/arch/x86/kernel/cpu/mce/core.c
> > +++ b/arch/x86/kernel/cpu/mce/core.c
> > @@ -1951,8 +1951,11 @@ static void apply_quirks_amd(struct cpuinfo_x86 *c)
> >  	if (c->x86 == 0x15 && c->x86_model <= 0xf)
> >  		mce_flags.overflow_recov = 1;
> >  
> > -	if (c->x86 >= 0x17 && c->x86 <= 0x1A)
> > -		mce_flags.zen_ifu_quirk = 1;
> > +	mce_flags.zen_ifu_quirk = cpu_feature_enabled(X86_FEATURE_ZEN1) ||
> > +				  cpu_feature_enabled(X86_FEATURE_ZEN2) ||
> > +				  cpu_feature_enabled(X86_FEATURE_ZEN3) ||
> > +				  cpu_feature_enabled(X86_FEATURE_ZEN4) ||
> > +				  cpu_feature_enabled(X86_FEATURE_ZEN5);
> 
> I was fearing this day would come where we'd need something like that and it
> would look gross. And it does.
> 
> Can't we simplify the quirk to do:
> 
> 	if (!m->cs)
> 		m->cs = regs->cs;
> 
> when X86_FEATURE_ZEN is set and that should be good enough if we squint our
> eyes hard enough...

The quirk doesn't apply to all Zen-based systems. Only the Zen 1-5 are
affected.

We could *not* do this patch if it's too ugly. The quirk would apply to
some systems that aren't affected. But this would be a NOP in practice.

> 
> m->cs on the fixed machines won't be 0 so it all just works...
> 
> -- 

I've been thinking that we could do away with some of these quirks if we
refactor a bit. I'll dust off a patch I have and send for RFC.

Thanks,
Yazen

      reply	other threads:[~2025-08-12 14:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-11 20:34 Yazen Ghannam
2025-08-11 20:55 ` Borislav Petkov
2025-08-12 14:56   ` Yazen Ghannam [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=20250812145638.GA383670@yaz-khff2.amd.com \
    --to=yazen.ghannam@amd.com \
    --cc=bp@alien8.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.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

all inboxes | Powered by JetHome®