[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [PATCH] 0/2 VCPU creation and allocation
I've put together two patches. The first introduces a new dom0_op, set_max_vcpus, which with an associated variable and a check in the VCPUOP handler fixes [1]bug 288. Also included is a new VCPUOP, VCPUOP_create, which handles all of the vcpu creation tasks and leaves initialization and unpausing to VCPUOP_initialize. The separation allows for build-time allocation of vcpus which becomes more important when trying to allocate memory in a NUMA-aware manner (i.e. knowing which physical cpus are being used in a domain before we allocate the memory). The second patch adds a new domain allocmap cpumap_t which is a bitmap of physical cpus from which vcpus are to be allocated. As vcpus are created, the selection of which physical cpu is balanced across the set of physical cpus within the map. The patch lets us control vcpu allocation at a high level (start all VCPUS on hyperthreads, NODE1, CPU2). 1. http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=288 -- Ryan Harper Software Engineer; Linux Technology Center IBM Corp., Austin, Tx (512) 838-9253 T/L: 678-9253 ryanh@xxxxxxxxxx _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |