| commit | e1638bd8588d780079e231b109ac94f0c281efda | |
| author | malc <malc@c046a42c-6fe2-441c-8c8c-71466251a162> | |
| Thu, 6 Nov 2008 18:54:46 +0000 (6 18:54 +0000) | ||
| committer | malc <malc@c046a42c-6fe2-441c-8c8c-71466251a162> | |
| Thu, 6 Nov 2008 18:54:46 +0000 (6 18:54 +0000) | ||
| tree | d6c0246ef556bfa38a5165d4a6880d86c84e84ac | treesnapshot (tar.gz zip) |
| parent | 6d946cdae0b5ba6b45499a124263b57ca5bffe68 | commitdiff |
Fix interrupt exclusion via SSTEP_NOIRQ
Commit #5620 revealed an issue of the SSTEP_NOIRQ masking that was
applied on all interrupt sources (including internal ones) when single
stepping through the guest. Due to that commit, we now ended up in an
infinite loop when CPU_INTERRUPT_EXIT was pending on SSTEP resume. That
was due to #5620 eating all TBs while CPU_INTERRUPT_EXIT is pending, but
SSTEP_NOIRQ preventing CPU_INTERRUPT_EXIT to be processed.
What SSTEP_NOIRQ should actually do is to block the delivery of all
external, guest visible interrupts. With the fix below applied, single
stepping now works again.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5643 c046a42c-6fe2-441c-8c8c-71466251a162
Commit #5620 revealed an issue of the SSTEP_NOIRQ masking that was
applied on all interrupt sources (including internal ones) when single
stepping through the guest. Due to that commit, we now ended up in an
infinite loop when CPU_INTERRUPT_EXIT was pending on SSTEP resume. That
was due to #5620 eating all TBs while CPU_INTERRUPT_EXIT is pending, but
SSTEP_NOIRQ preventing CPU_INTERRUPT_EXIT to be processed.
What SSTEP_NOIRQ should actually do is to block the delivery of all
external, guest visible interrupts. With the fix below applied, single
stepping now works again.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5643 c046a42c-6fe2-441c-8c8c-71466251a162
| cpu-exec.c | diffblobblamehistory |