1. 11 6月, 2015 5 次提交
  2. 04 6月, 2015 1 次提交
  3. 01 6月, 2015 2 次提交
  4. 31 5月, 2015 2 次提交
  5. 18 5月, 2015 2 次提交
  6. 11 5月, 2015 3 次提交
  7. 30 4月, 2015 2 次提交
  8. 28 4月, 2015 3 次提交
  9. 27 3月, 2015 1 次提交
  10. 25 3月, 2015 1 次提交
  11. 10 3月, 2015 3 次提交
  12. 09 3月, 2015 1 次提交
  13. 26 2月, 2015 6 次提交
  14. 24 2月, 2015 1 次提交
  15. 10 2月, 2015 3 次提交
  16. 06 2月, 2015 1 次提交
    • P
      rtl8139: simplify timer logic · 237c255c
      Paolo Bonzini 提交于
      Pavel Dovgalyuk reports that TimerExpire and the timer are not restored
      correctly on the receiving end of migration.
      
      It is not clear to me whether this is really the case, but we can take
      the occasion to get rid of the complicated code that computes PCSTimeout
      on the fly upon changes to IntrStatus/IntrMask.  Just always keep a
      timer running, it will fire every ~130 seconds at most if the interrupt
      is masked with TimerInt != 0.
      
      This makes rtl8139_set_next_tctr_time idempotent (when the virtual clock
      is stopped between two calls, as is the case during migration).
      
      Tested with Frediano's qtest.
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      Message-id: 1421765099-26190-1-git-send-email-pbonzini@redhat.com
      Signed-off-by: NStefan Hajnoczi <stefanha@redhat.com>
      237c255c
  17. 26 1月, 2015 1 次提交
  18. 12 1月, 2015 2 次提交