summaryrefslogtreecommitdiff
path: root/src/mainboard/intel/mtlrvp/Kconfig
diff options
context:
space:
mode:
authorShuo Liu <shuo.liu@intel.com>2024-03-26 21:27:52 +0800
committerLean Sheng Tan <sheng.tan@9elements.com>2024-05-02 14:31:51 +0000
commit5ed9fe94972e8383edd7929ccce4d9b73823a362 (patch)
tree3634e5caec445a56323ecc54022bca7b2d6dc7f7 /src/mainboard/intel/mtlrvp/Kconfig
parent1c39bccf7228252e126d565488f73baeef084c53 (diff)
soc/intel/xeon_sp: Add device to proximity domain map utils
In NUMA architecture, all devices (cpu, memory and PCI device) belong to specific proximity domain. Add utils to map device instance to their proximity domain. Proximity domain ID is the index assigned at the creation of proximity domains. There is no hard relationship between proximity domain ID and the device identities (e.g. socket ID). Hence we need the map utils to explicitly link them. For now the Sub-NUMA config isn't taken into account. TEST=Build and boot on intel/archercity CRB Change-Id: Icd14a98823491ccfc38473e44a26dddfbbcaa7c0 Signed-off-by: Shuo Liu <shuo.liu@intel.com> Co-authored-by: Ziang Wang <ziang.wang@intel.com> Co-authored-by: Gang Chen <gang.c.chen@intel.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/81440 Reviewed-by: Angel Pons <th3fanbus@gmail.com> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'src/mainboard/intel/mtlrvp/Kconfig')
0 files changed, 0 insertions, 0 deletions