diff options
| author | Rik van Riel <riel@redhat.com> | 2012-06-20 00:51:04 +0400 |
|---|---|---|
| committer | Marcelo Tosatti <mtosatti@redhat.com> | 2012-07-06 21:11:18 +0400 |
| commit | 5cfc2aabcb282f4554e7086c9893b386ad6ba9d4 (patch) | |
| tree | 81b9989c069f54e42a748c8af6a2989bdbe6a8b9 /drivers/firmware/Kconfig | |
| parent | 21b26c08535c992802402c7ba2d789ca9e1a5707 (diff) | |
| download | linux-5cfc2aabcb282f4554e7086c9893b386ad6ba9d4.tar.xz | |
KVM: handle last_boosted_vcpu = 0 case
If last_boosted_vcpu == 0, then we fall through all test cases and
may end up with all VCPUs pouncing on vcpu 0. With a large enough
guest, this can result in enormous runqueue lock contention, which
can prevent vcpu0 from running, leading to a livelock.
Changing < to <= makes sure we properly handle that case.
Signed-off-by: Rik van Riel <riel@redhat.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Diffstat (limited to 'drivers/firmware/Kconfig')
0 files changed, 0 insertions, 0 deletions