1. 10 11月, 2008 4 次提交
  2. 09 11月, 2008 6 次提交
  3. 08 11月, 2008 4 次提交
  4. 07 11月, 2008 5 次提交
  5. 06 11月, 2008 14 次提交
  6. 05 11月, 2008 6 次提交
  7. 04 11月, 2008 1 次提交
    • M
      Add safety net against potential infinite loop · 55e8b85e
      malc 提交于
      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
      55e8b85e