On 2/11/25 11:43, Sohil Mehta wrote: > The Family model check to read the processor flag MSR is misleading and > potentially incorrect. It doesn't consider Family while comparing the > model number. The original check did have a Family number but it got > lost/moved during refactoring. > > intel_collect_cpu_info() is called through multiple paths such as early > initialization, CPU hotplug as well as IFS image load. Some of these > flows would be error prone due to the ambiguous check. > > Correct the processor flag scan check to use a Family number and update > it to a VFM based one to make it more readable. Acked-by: Dave Hansen <dave.hansen@xxxxxxxxxxxxxxx>
