On 2/10/26 15:52, Luck, Tony wrote:
>> Is the PECI model list growing all the time? Like will it grow for the
>> next decade?
> Looks like this started in Feb 2022 with HASWELL ... ICELAKE
> 
> July 2023 added SAPPHIRE. October 2025 added EMERALD.
> 
> Maybe Iwona can future predictions/details when she sees this e-mail thread.

I went and looked at this a bit more. I think we're going to way too
much trouble to share a few constants. It was a valiant effort on the
part of the PECI folks to avoid duplication, but I think it's run its
course.

The x86 code wants and needs to know the logically separate
model/family/stepping. We have oodles of

	if (model == INTEL_FOO)
		do_foo_thing();

But we basically never care about the format that's in CPUID.01H:EAX.

The PECI code has none of that. It's *just* matching the "id" of the
device to the "id" of the CPU. It just so happens that the "id" that's
chosen matches CPUID.01H:EAX.

So PECI and x86 both want the same data, but they do very different
things with it.

So let's just duplicate the constants. Completely untested patch attached.

Any reason not to do this?