On 11/23/2010 02:16 AM, Dor Laor wrote:
On 11/23/2010 08:41 AM, Avi Kivity wrote:
On 11/23/2010 01:00 AM, Anthony Liguori wrote:
qemu-kvm vcpu threads don't response to SIGSTOP/SIGCONT. Instead of
teaching
them to respond to these signals, introduce monitor commands that stop
and start
individual vcpus.
The purpose of these commands are to implement CPU hard limits using
an external
tool that watches the CPU consumption and stops the CPU as appropriate.
Why not use cgroup for that?
This is a stop-gap.
The cgroup solution isn't perfect. It doesn't know anything about guest
time verses hypervisor time so it can't account just the guest time like
we do with this implementation. Also, since it may deschedule the vcpu
thread while it's holding the qemu_mutex, it may unfairly tax other vcpu
threads by creating additional lock contention.
This is all solvable but if there's an alternative that just requires a
small change to qemu, it's worth doing in the short term.
Regards,
Anthony Liguori
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
