AMD F17 core topology is per process node
When introducing the new AMD core topology I made a mistake. To determine the package core ID, I used the extended leaf 0x15 ebx register. This has the core id in it. However, this is the core ID within the package. This means that the way we've calculated the package core isn't actually unique to the package (the whole physical chip), but rather unique to the process node, of which there are multiple inside. This can cause several problems. The solution is to calculate this like we do on Intel by leveraging the APIC ID relationship.
Updated by Electric Monk about 1 year ago
- Status changed from New to Closed
commit 15a5383b049109e4ce37a4a457a933812f189141 Author: Robert Mustacchi <firstname.lastname@example.org> Date: 2019-07-10T15:49:19.000Z 11279 AMD F17 core topology is per process node Reviewed by: John Levon <email@example.com> Reviewed by: Patrick Mooney <firstname.lastname@example.org> Reviewed by: Dan McDonald <email@example.com> Reviewed by: Richard Lowe <firstname.lastname@example.org> Reviewed by: Toomas Soome <email@example.com> Approved by: Garrett D'Amore <firstname.lastname@example.org>