On 12/14/2011 02:16 PM, Marcelo Tosatti wrote: > > Having this controlled from userspace means it doesn't work for SIGSTOP > > or for long scheduling delays. What about doing this automatically > > based on preempt notifiers? > > Long scheduling delays should be considered hangups from the guest > perspective. Why? To the guest it looks like slow hardware, but it will interpret it as a softlockup. > About SIGSTOP, that is a corner case. Unsure if its even properly supported > by QEMU. It works from my experience. -- 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
