Description
A clear and concise description of what the bug is.
The NUMA probe is processing only comma-separated list of CPU threads but the kernel could provide a list of ranges too, separated by a dash.
To Reproduce
- Define VM with the following example CPU Topology (Not sure is it needed, but tested on CentOS 7 with qemu-kvm-ev):
<cpu mode='host-passthrough' check='none'>
<topology sockets='2' cores='8' threads='2'/>
<numa>
<cell id='0' cpus='0-15' memory='3145728' unit='KiB'/>
<cell id='1' cpus='16-31' memory='3145728' unit='KiB'/>
</numa>
</cpu>
- Run the numa probe in the VM - the probe will return CPUS = "0-1" instead of a comma separated list.
Expected behavior
The NUMA probe should return all siblings for the given core
Details
- Affected Component: [Monitoring]
- Hypervisor: [KVM]
- Version: [development]
Additional context
I'd propose to use of a normalizing function that will return all threads even on POWER7 and POWER8 ;)
Progress Status
Description
A clear and concise description of what the bug is.
The NUMA probe is processing only comma-separated list of CPU threads but the kernel could provide a list of ranges too, separated by a dash.
To Reproduce
Expected behavior
The NUMA probe should return all siblings for the given core
Details
Additional context
I'd propose to use of a normalizing function that will return all threads even on POWER7 and POWER8 ;)
Progress Status