On Thu, Jul 21, 2011 at 10:08:03AM +0800, Wen Congyang wrote:
Introduce the function virCgroupForVcpu() to create sub directory for
each vcpu.
I'm far from convinced that this is a good idea. Setting policies on
individual VCPUs is giving the host admin a misleading illusion of
control over individual guest VCPUs. The problem is that QEMU has
many non-VCPU threads which consume non-trivial CPU time. CPU time
generated by a CPU in the guest, does not neccessarily map to a VCPU
thread in the host, but could instead go to a I/O thread or a display
thread, etc.
IMHO we should only be doing controls at the whole VM level here.
Daniel
--
|:
http://berrange.com -o-
http://www.flickr.com/photos/dberrange/ :|
|:
http://libvirt.org -o-
http://virt-manager.org :|
|:
http://autobuild.org -o-
http://search.cpan.org/~danberr/ :|
|:
http://entangle-photo.org -o-
http://live.gnome.org/gtk-vnc :|