1. 03 11月, 2014 1 次提交
    • L
      target-mips: add KScratch registers · e98c0d17
      Leon Alrae 提交于
      KScratch<n> Registers (CP0 Register 31, Selects 2 to 7)
      
      The KScratch registers are read/write registers available for scratch pad
      storage by kernel mode software. They are 32-bits in width for 32-bit
      processors and 64-bits for 64-bit processors.
      
      CP0Config4.KScrExist[2:7] bits indicate presence of CP0_KScratch1-6 registers.
      For Release 6, all KScratch registers are required.
      Signed-off-by: NLeon Alrae <leon.alrae@imgtec.com>
      Reviewed-by: NYongbok Kim <yongbok.kim@imgtec.com>
      e98c0d17
  2. 14 10月, 2014 9 次提交
  3. 13 10月, 2014 12 次提交
  4. 12 8月, 2014 1 次提交
  5. 29 7月, 2014 1 次提交
  6. 05 7月, 2014 1 次提交
  7. 21 6月, 2014 1 次提交
  8. 19 6月, 2014 1 次提交
  9. 18 6月, 2014 1 次提交
    • J
      target-mips: Reset CPU timer consistently · 4b69c7e2
      James Hogan 提交于
      The MIPS CPU timer (CP0 Count/Compare registers & QEMU timer) is
      reset at machine initialisation, including starting the timeout. Both
      registers however are placed before mvp in CPUMIPSState so they will
      both be zeroed on reset by the memset in mips_cpu_reset() including soon
      after init. This doesn't take into account that the timer may be
      running, in which case env->CP0_Count will represent the delta against
      the VM clock and the timeout will need updating.
      
      At init time (cpu_mips_clock_init()), lets only create the timer.
      Setting Count = 1 and starting the timer (cpu_mips_store_count()) can be
      done at reset time from cpu_state_reset(), which is after the memset.
      There is also no need to set CP0_Compare = 0 as that is already handled
      by the memset.
      
      Note that a reset occurs from mips_cpu_realizefn() which is before the
      machine init callback has had a chance to set up the CPU interrupts and
      the CPU timer, so env->timer will be NULL. This case is handled
      explicitly in cpu_mips_store_count(), treating the timer as disabled
      (which will also be the right thing to do when KVM support is added).
      Reported-by: NPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: NJames Hogan <james.hogan@imgtec.com>
      Cc: Aurelien Jarno <aurelien@aurel32.net>
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      4b69c7e2
  10. 05 6月, 2014 1 次提交
  11. 29 5月, 2014 1 次提交
  12. 26 3月, 2014 1 次提交
  13. 14 3月, 2014 2 次提交
  14. 10 2月, 2014 3 次提交
  15. 21 12月, 2013 1 次提交
  16. 09 12月, 2013 1 次提交
  17. 11 10月, 2013 1 次提交
  18. 07 10月, 2013 1 次提交