| commit | 8c14c17395809dfb2b20bd3598e067d2c5af7dc4 | |
| author | Jan Kiszka <jan.kiszka@web.de> | |
| Sat, 30 May 2009 08:01:45 +0000 (30 10:01 +0200) | ||
| committer | Anthony Liguori <aliguori@us.ibm.com> | |
| Tue, 16 Jun 2009 20:36:47 +0000 (16 15:36 -0500) | ||
| tree | fbe326566bbbea7fd89f19078f145906fe4878e2 | treesnapshot (tar.gz zip) |
| parent | 6a7ad2998ca47711eddd191caa1a95f14459793f | commitdiff |
kvm: Fix IRQ injection into full queue
User space may only inject interrupts during kvm_arch_pre_run if
ready_for_interrupt_injection is set in kvm_run. But that field is
updated on exit from KVM_RUN, so we must ensure that we enter the
kernel after potentially queuing an interrupt, otherwise we risk to
loose one - like it happens with the current code against latest
kernel modules (since kvm-86) that started to queue only a single
interrupt.
Fix the problem by reordering kvm_cpu_exec.
Credits go to Gleb Natapov for analyzing the issue in details.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
User space may only inject interrupts during kvm_arch_pre_run if
ready_for_interrupt_injection is set in kvm_run. But that field is
updated on exit from KVM_RUN, so we must ensure that we enter the
kernel after potentially queuing an interrupt, otherwise we risk to
loose one - like it happens with the current code against latest
kernel modules (since kvm-86) that started to queue only a single
interrupt.
Fix the problem by reordering kvm_cpu_exec.
Credits go to Gleb Natapov for analyzing the issue in details.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
| kvm-all.c | diffblobblamehistory |