From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: [edk2-devel] [edk2platforms][PATCH v1 1/1] IntelSiliconPkg: Add IntelDieInfoProtocol To: Ni, Ray ,devel@edk2.groups.io From: "Maciej Czajkowski" X-Originating-Location: Leixlip, Leinster, IE (192.198.151.52) X-Originating-Platform: Windows Chrome 94 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Fri, 15 Oct 2021 04:21:09 -0700 References: In-Reply-To: Message-ID: <18322.1634296869638692591@groups.io> Content-Type: multipart/alternative; boundary="LeyYIeW8eDD1ohkpggkd" --LeyYIeW8eDD1ohkpggkd Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable What's the difference between SOC and CPU? SOC die differs from typical CPU die in Intel's chiplet design. What the purpose of "DieIndex"? We want to have an indication to which exactly die given protocol instance = is referring to (in example in multi socket/multi PCH designs). Have you considered to use data fields such as "CONST CHAR8 * DieName, Step= ping, Sku" instead of the methods? Yes, but there might be a configuration where chipset id is going to be cha= nged during the boot. By using methods, we ensure that returned value is co= rrect in every call. Regards, Maciej --LeyYIeW8eDD1ohkpggkd Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
What's the difference between SOC= and CPU?
SOC die differs from typical CPU die = in Intel's chiplet design.
 
What the purpose of "DieIndex"?
We want to have an indication to whic= h exactly die given protocol instance is referring to (in example in multi = socket/multi PCH designs).
 
Have you considered to use data f= ields such as "CONST CHAR8 * DieName, Stepping, Sku" instead of the methods= ?
Yes, but there might be a configurati= on where chipset id is going to be changed during the boot. By using method= s, we ensure that returned value is correct in every call.

Regar= ds,
Maciej
--LeyYIeW8eDD1ohkpggkd--