Le 26/05/2021 à 15:23, Samuel Thibault a écrit :
Brice Goglin, le mer. 26 mai 2021 14:13:02 +0200, a ecrit:
os_index is already *unsigned* in the API (did you mean signed?). We cannot
change the obj->os_index back to signed now, it would break existing users.
Mmm, it wouldn't break the ABI,
Brice Goglin, le mer. 26 mai 2021 14:13:02 +0200, a ecrit:
> os_index is already *unsigned* in the API (did you mean signed?). We cannot
> change the obj->os_index back to signed now, it would break existing users.
Mmm, it wouldn't break the ABI, only printf formats using %u?
Samuel
Merci beaucoup!
BTW, it seems that lstopo does not print indexes when the value is
HWLOC_UNKNOWN_INDEX
$ lstopo --physical --allow all
Machine (31GB total)
Package
NUMANode P#0 (26GB)
L3 (4096KB) + Core P#0
L2 (1024KB) + L1d (32KB) + L1i (48KB)
Die + PU P#0
PU P#2
Le 26/05/2021 à 14:24, Jirka Hladky a écrit :
However maybe debugging would be easier if tools printed that
special value as -1 instead of 4294967295 (I'd need to check other
tools too, lstopo takes care of some of these values, maybe not all).
I agree. So perhaps we can update
Hi Brice,
thanks for looking into this!
Package ID seems to be properly set on POWER8/9 machines I have access to.
> Maybe something related to LPAR exposing a special/virtual topology hence
> die and package ID wouldn't make sense?
Yes, it sounds plausible. I will try to find out.
os_index
Le 26/05/2021 à 13:51, Jirka Hladky a écrit :
Hi Brice,
I would like to get your opinion on the following issue. On IBM LPAR,
kernel reports die_id and physical_package_id to be -1.
See [0]
hwloc-calc converts these values into an unsigned integer, resulting
in Socket ID 2^32-1:
Hi Brice,
I would like to get your opinion on the following issue. On IBM LPAR,
kernel reports die_id and physical_package_id to be -1. See [0]
hwloc-calc converts these values into an unsigned integer, resulting in
Socket ID 2^32-1:
hwloc-calc --physical-output --intersect socket core:0
