[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yh59WcIr06mK9aK2@kroah.com>
Date: Tue, 1 Mar 2022 21:08:57 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Jithu Joseph <jithu.joseph@...el.com>
Cc: hdegoede@...hat.com, markgross@...nel.org, tglx@...utronix.de,
mingo@...hat.com, bp@...en8.de, dave.hansen@...ux.intel.com,
x86@...nel.org, hpa@...or.com, corbet@....net,
andriy.shevchenko@...ux.intel.com, ashok.raj@...el.com,
tony.luck@...el.com, rostedt@...dmis.org,
linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
platform-driver-x86@...r.kernel.org, patches@...ts.linux.dev,
ravi.v.shankar@...el.com
Subject: Re: [RFC 01/10] x86/microcode/intel: expose collect_cpu_info_early()
for IFS
On Tue, Mar 01, 2022 at 11:54:48AM -0800, Jithu Joseph wrote:
> IFS uses a image provided by Intel that can be regarded as firmware.
> IFS image carries the Processor Signature such as family/model/stepping
> similar to what we find in the microcode header.
>
> Expose collect_cpu_info_early() and cpu_signatures_match() for IFS image
If this is going to be a global symbol, how about
cpu_collect_info_early() to keep the correct prefix?
thanks,
greg k-h
Powered by blists - more mailing lists