I'm sending a first draft of my proposed cpu hotplug driver for kvm/virtio
The first patch is the kernel module, while the second, the userspace pci 
device.

The host boots with the maximum cpus it should ever use, through the -smp 
parameter.
Due to real machine constraints (which qemu copies), i386 does not allow for 
any addition
of cpus after boot, so this is the most general way.

I do however, include an "attempt_buffer" in the userspace part. It's purpose 
is to
allow tools like virt-manager to set a max_cpus (-smp), and a desired number of 
cpus
in their configuration files. (and AFAICT, there's is no easy way for them to 
tell when the
backend driver is up and running)

Other than that, it should be pretty much straightforward.

Looking forward for your comments


_______________________________________________
Virtualization mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/virtualization

Reply via email to