RE: [Xen-devel] [PATCH] xend: update cpu config option

["Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>]

 > The 'cpu' option in domain config files will pin VCPU0 of a domain.
> This is not as useful now that domains can have more than 1 
> vcpu.  This patch changes 'cpu' to 'cpus' and takes a list of 
> physical cpus the domains' vcpus can use and will pin the 
> vcpus upon domain creation.
> 
> cpus = [1]      # this starts all domain vcpus pinned to CPU1

I think this patch is generally a good thing. Should we support cpu= as
backward compatible legacy option?
 
> The list is circular, so in a domain with the following config:
> 
> vcpus = 4
> cpus  = [0,3,7]  # Use any of 0, 3, 7 for this domain.
> 
> would see vcpus 0-3 pinned to cpus 0,3,7,0 respectively.

Actually, although this is a reasonable syntax, I think we'll probably
interpret it differently in future when we have CPU load ballancing: I
think we'll want to list the set of CPUs that a given _domain_ can use
rather than pining individual CPUs.

However, I wander whether this should be a string so that we can list
e.g. cpus='0-3,5,^1'


Ian

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel