> > Also included is a new VCPUOP,
> > VCPUOP_create, which handles all of the vcpu creation tasks 
> and leaves 
> > initialization and unpausing to VCPUOP_initialize.
>
> I think two new Xen operations is one too many.
>
> Either we should take set_max_vcpus, and have that implicitly 
> do the work of VCPUOP_create, or we should take VCPUOP_create 
> (callable only by domain0) and have that implicitly increase 
> max_vcpus for the subject domain.
While we're at it, let's clean up the xm commands too. I tihnk its
pointless letting the user specify the vcpu they want to enable/disable.
Let's change the command names to vcpu-add / vcpu-remove and have them
work on the lowest numbered free vcpu in the case of vcpu-add and the
highest currently active in the case of vcpu-remove.
 
Ian
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel