| commit | 55e8b85e4891dafd0d0222ad1ced78e3c5f24e1e | |
| author | malc <malc@c046a42c-6fe2-441c-8c8c-71466251a162> | |
| Tue, 4 Nov 2008 14:18:13 +0000 (4 14:18 +0000) | ||
| committer | malc <malc@c046a42c-6fe2-441c-8c8c-71466251a162> | |
| Tue, 4 Nov 2008 14:18:13 +0000 (4 14:18 +0000) | ||
| tree | a9f89f6536dff7bbc0c79539ee1c3d8e785dd11a | treesnapshot (tar.gz zip) |
| parent | 0c5f3c8d7d77307d79c6f764ef62ce6ffb3bc9e8 | commitdiff |
Add safety net against potential infinite loop
cpu_interrupt might be called while translating the TB, but before it
is linked into a potentially infinite loop and becomes env->current_tb.
Currently this can (and does) cause huge problems only when using
dyntick clock, with other (periodic) clocks host_alarm_handler will
eventually be executed resulting in a call to cpu_interrupt which will
reset the recursion of running TB and the damage is "only" latency.
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5620 c046a42c-6fe2-441c-8c8c-71466251a162
cpu_interrupt might be called while translating the TB, but before it
is linked into a potentially infinite loop and becomes env->current_tb.
Currently this can (and does) cause huge problems only when using
dyntick clock, with other (periodic) clocks host_alarm_handler will
eventually be executed resulting in a call to cpu_interrupt which will
reset the recursion of running TB and the damage is "only" latency.
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5620 c046a42c-6fe2-441c-8c8c-71466251a162
| cpu-exec.c | diffblobblamehistory |