1. 13 Sep, 2020 13 commits
  2. 12 Sep, 2020 2 commits
  3. 01 Sep, 2020 1 commit
  4. 31 Aug, 2020 9 commits
  5. 26 Aug, 2020 2 commits
  6. 25 Aug, 2020 2 commits
  7. 12 Aug, 2020 1 commit
    • Martin Quinson's avatar
      Make sure that VM::get_speed() returns the correct value after a migration · 46b3f69b
      Martin Quinson authored
      For that, I reset the physical fields of the CPU (speed_, pstate_ and
      speed_per_pstate_) to the ones of the new physical host during the
      migration.
      
      Maybe we should change only the speed_, and prevent the use of pstate
      things in VM?
      
      Another approach for this commit could be to make Host::get_speed()
      and friend virtual, and to override them in the VM to use the values
      of the underlying physical CPU (ie, of get_pm()->pimple_cpu) instead
      of the one of the VM's VCPU, but I fear to still use the wrong speed
      in some cases, in particular when a new execution in created onto the
      VCPU.
      
      This forbids speed_per_pstate_ to be 'const', since we reset it for
      VCPUs on VM migration. Another approach could have been to destroy and
      re-create the VCPU on migration, but I'd have to update the LMM to
      point the Execs to the newly created resource, which seems
      troublesome.
      46b3f69b
  8. 11 Aug, 2020 2 commits
  9. 27 Jul, 2020 3 commits
  10. 25 Jul, 2020 1 commit
  11. 17 Jul, 2020 1 commit
  12. 16 Jul, 2020 1 commit
  13. 15 Jul, 2020 2 commits