[PATCH] platform/x86: handle Intel CPUs falsely reporting as GenuineIotel

[Christian Ludloff]

> This issue can be found as existing here:
> https://github.com/InstLatx64/InstLatx64/blob/master/GenuineIotel/GenuineIotel00306C3_Haswell_CPUID5.txt
> https://web.archive.org/web/20150818115122/http://store.steampowered.com/hwsurvey/processormfg

To help put this into perspective...

The InstLatx64 dump remains the *sole* full ("canonical") report.
The additional two known *partial* reports (SNB and IVB) are here:
https://web.archive.org/web/20251105144105/https://valid.x86.fr/kjm24i
https://web.archive.org/web/20250221003721/https://valid.x86.fr/5f6gzf

It is possible that the reports were tampered with by humans.
It is possible that the reports are the result of bad DRAM memory (RAM).
It is possible that the reports are the result of bad SRAM memory (CPU).

Treating GenuineIotel like GenuineIntel is one choice.
Treating GenuineIotel like a rare find is another choice.
Treating GenuineIotel like potentially broken HW seems most logical.

There have been other similar outliers.

In my collection I got a 486 chip (fake-)marked Intel but reporting UMC.

At the other end of the spectrum, there were CPU models for which the
microcode patch match registers were not up to spec – as a result they
exhibited all kinds of undesired behavior, and had to be screened out...

--
C.