[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a292492e-d922-e964-cc60-ac05ffdee1ed@intel.com>
Date: Tue, 1 Mar 2022 16:56:59 -0800
From: "Joseph, Jithu" <jithu.joseph@...el.com>
To: Greg KH <gregkh@...uxfoundation.org>
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 3/1/2022 12:08 PM, Greg KH wrote:
> 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?
Will make this change
Powered by blists - more mailing lists