Revision 313f636d5c490c9741d3f750dc8da33029edbc6b authored by David Matlack on 09 March 2016, 00:19:44 UTC, committed by Paolo Bonzini on 09 March 2016, 10:54:14 UTC
When growing halt-polling, there is no check that the poll time exceeds
the limit. It's possible for vcpu->halt_poll_ns grow once past
halt_poll_ns, and stay there until a halt which takes longer than
vcpu->halt_poll_ns. For example, booting a Linux guest with
halt_poll_ns=11000:

 ... kvm:kvm_halt_poll_ns: vcpu 0: halt_poll_ns 0 (shrink 10000)
 ... kvm:kvm_halt_poll_ns: vcpu 0: halt_poll_ns 10000 (grow 0)
 ... kvm:kvm_halt_poll_ns: vcpu 0: halt_poll_ns 20000 (grow 10000)

Signed-off-by: David Matlack <dmatlack@google.com>
Fixes: aca6ff29c4063a8d467cdee241e6b3bf7dc4a171
Cc: stable@vger.kernel.org
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
1 parent 9522b37
History
File Mode Size
algos
busses
muxes
Kconfig -rw-r--r-- 4.4 KB
Makefile -rw-r--r-- 449 bytes
i2c-boardinfo.c -rw-r--r-- 2.8 KB
i2c-core.c -rw-r--r-- 86.9 KB
i2c-core.h -rw-r--r-- 950 bytes
i2c-dev.c -rw-r--r-- 17.7 KB
i2c-mux.c -rw-r--r-- 6.2 KB
i2c-slave-eeprom.c -rw-r--r-- 4.5 KB
i2c-smbus.c -rw-r--r-- 6.7 KB
i2c-stub.c -rw-r--r-- 10.3 KB

back to top