init-dom0less: Weird use of cpupool in xl dominfo

[Amneesh Singh <a-singh21@xxxxxx>]

Hello, I was going through the source code for init-dom0less as I was
facing some issue after applying this patchset. Feel free to ignore it
however, as it seems unrelated to the issue I am encountering.

https://lists.xenproject.org/archives/html/xen-devel/2024-05/msg01825.html

One peculiar thing I noticed was that the "cpupool" field is being used
as a bitfield to check individual vCPUs. However afaik, "cpupool" is
supposed to be the cpupool *ID*. That matches the fact that the cpupool
value for all my VMs is 0, as I only have a single cpupool (id = 0). Am
I overlooking something, or am I correct? Here is the relevant code:

https://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=tools/helpers/init-dom0less.c;h=fee93459c4b9da59446a2f8dfcf5cbfc4d95aeab;hb=HEAD#l176

Regards
Amneesh