|
xen-devel
RE: [Xen-devel] [PATCH] xen, tools/python/xen: pincpu support vcpus, add
> The following patch updates the dom0 pincpu operation to read
> the VCPU value from the xend interface rather than
> hard-coding the exec_domain to 0. This prevented pinning
> VCPUS other than 0 to a particular cpu. I added the number
> of VCPUS to the main xm list output and also included a new
> sub-option to xm list to display the VCPU to CPU mapping.
> While working on the pincpu code, I fixed an out-of-bounds
> indexing for the pincpu operation that wasn't previously
> exposed since the vcpu/exec_domain value was hard-coded to 0.
Ryan, good progress, but I'd like to propose a couple of extentions:
It would be useful if you could update it so that pincpu enabled you to
specify a set of physical CPUs for each VCPU e.g.
"xm pincpu mydom 1 2,4-6" which would allow VCPU 1 of mydom to run on
CPUs 2,4 and 5 but no others. -1 would still mean "run anywhere". Having
this functionality is really important before we can implement any kind
of CPU load ballancer.
Secondly, I think it would be really good if we could have some
hierarchy in CPU names. Imagine a 4 socket system with dual core hyper
threaded CPUs. It would be nice to be able to specify the 3rd socket,
1st core, 2nd hyperthread as CPU "2.0.1".
Where we're on a system without one of the levels of hierarchy, we just
miss it off. E.g. a current SMP Xeon box would be "x.y". This would be
much less confusing than the current scalar representation.
What do you think?
Thanks,
Ian
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
Home