On 3 Oct 2005, at 22:07, Ryan Harper wrote:
I was also thinking toward NUMA systems where I'd like to know which
physical cpus are being utilized for a given domain so when we allocate
memory for a domain we can try to localize those allocations to the
cpus
that will be using it. Currently domain memory allocation happens
before secondary processors are selected.
I'd rather see domain creation take both max_vcpus and cpu placement
bitmaps instead, but if that is not acceptable for 3.0, I'll go ahead
and work up the patch as described since it needs to be resolved for
3.0.
I'd rather keep single-purpose dom0 ops than have createdomain become a
'union of everything'.
There is already a dom0 op for pinning a vcpu. Right now it can't be
used before the domain starts for other than vcpu0 since it requires
VCPUOP_create to allocate the vcpu structure, but fixing that is
unrelated to whether pin info is passed to DOM0_CREATEDOMAIN. As you
say, it's also not critical to fix for 3.0.
-- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel