On 04/05/2011 12:03 PM, Peter Zijlstra wrote:
On Tue, 2011-04-05 at 11:56 +0300, Avi Kivity wrote: > > Could be waking up due to guest wakeups, or qemu internal wakeups > (display refresh) or due to guest timer sources which are masked away in > the guest (if that's the case we should optimize it away). Right, so I guess we're all clutching at straws here :-) Ben how usable is that system when its in that state? Could you run a function trace or a trace with all kvm and sched trace-events enabled?
Ben, to do that, look up http://www.linux-kvm.org/page/Tracing; the command for combined sched/kvm tracing is
# trace-cmd record -b 20000 -e kvm -e sched -- error compiling committee.c: too many arguments to function -- 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
