[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240425104624.GCZio0gDJABGjzoan1@fat_crate.local>
Date: Thu, 25 Apr 2024 12:46:24 +0200
From: Borislav Petkov <bp@...en8.de>
To: Tony Luck <tony.luck@...el.com>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
"H. Peter Anvin" <hpa@...or.com>,
Luis Chamberlain <mcgrof@...nel.org>,
Paolo Bonzini <pbonzini@...hat.com>,
Ashok Raj <ashok.raj@...el.com>, Bingsong Si <sibs@...natelecom.cn>,
linux-kernel@...r.kernel.org, patches@...ts.linux.dev
Subject: Re: [PATCH v4 29/71] x86/cpu/intel: Switch to new Intel CPU model
defines
On Wed, Apr 24, 2024 at 11:15:08AM -0700, Tony Luck wrote:
> +static bool vfm_match(struct cpuinfo_x86 *c, u32 vfm)
> +{
> + return c->x86_vendor == VFM_VENDOR(vfm) &&
> + c->x86 == VFM_FAMILY(vfm) &&
> + c->x86_model == VFM_MODEL(vfm);
> +}
Why is that one here?
It looks generic enough to put it in asm/processor.h so that it can get
used elsewhere too instead of homegrowing things again...
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists