1. 09 9月, 2015 1 次提交
  2. 15 8月, 2015 1 次提交
    • P
      exec: drop cpu_can_do_io, just read cpu->can_do_io · 414b15c9
      Paolo Bonzini 提交于
      After commit 626cf8f4 (icount: set can_do_io outside TB execution,
      2014-12-08), can_do_io is set to 1 if not executing code.  It is
      no longer necessary to make this assumption in cpu_can_do_io.
      
      It is also possible to remove the use_icount test, simply by
      never setting cpu->can_do_io to 0 unless use_icount is true.
      
      With these changes cpu_can_do_io boils down to a read of
      cpu->can_do_io.
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      414b15c9
  3. 09 7月, 2015 2 次提交
  4. 19 3月, 2015 1 次提交
  5. 18 2月, 2015 1 次提交
  6. 21 12月, 2014 1 次提交
  7. 02 11月, 2014 1 次提交
  8. 26 9月, 2014 2 次提交
  9. 12 9月, 2014 1 次提交
  10. 30 6月, 2014 1 次提交
  11. 14 3月, 2014 9 次提交
  12. 23 12月, 2013 2 次提交
  13. 20 9月, 2013 1 次提交
    • J
      cpu: Move cpu state syncs up into cpu_dump_state() · 97577fd4
      James Hogan 提交于
      The x86 and ppc targets call cpu_synchronize_state() from their
      *_cpu_dump_state() callbacks to ensure that up to date state is dumped
      when KVM is enabled (for example when a KVM internal error occurs).
      
      Move this call up into the generic cpu_dump_state() function so that
      other KVM targets (namely MIPS) can take advantage of it.
      
      This requires kvm_cpu_synchronize_state() and cpu_synchronize_state() to
      be moved out of the #ifdef NEED_CPU_H in <sysemu/kvm.h> so that they're
      accessible to qom/cpu.c.
      Signed-off-by: NJames Hogan <james.hogan@imgtec.com>
      Cc: Andreas Färber <afaerber@suse.de>
      Cc: Alexander Graf <agraf@suse.de>
      Cc: Gleb Natapov <gleb@redhat.com>
      Cc: qemu-ppc@nongnu.org
      Cc: kvm@vger.kernel.org
      Signed-off-by: NGleb Natapov <gleb@redhat.com>
      97577fd4
  14. 03 9月, 2013 1 次提交
  15. 17 8月, 2013 1 次提交
  16. 29 7月, 2013 1 次提交
    • A
      cpu: Partially revert "cpu: Change qemu_init_vcpu() argument to CPUState" · 14a10fc3
      Andreas Färber 提交于
      Commit c643bed9 moved qemu_init_vcpu() calls to common CPUState code.
      This causes x86 cpu-add to fail with "KVM: setting VAPIC address failed".
      
      The reason for the failure is that CPUClass::kvm_fd is not yet
      initialized in the following call graph:
      ->x86_cpu_realizefn
       ->x86_cpu_apic_realize
        ->qdev_init
         ->device_set_realized
          ->device_reset (hotplugged == 1)
           ->apic_reset_common
            ->vapic_base_update
             ->kvm_apic_vapic_base_update
      This causes attempted KVM vCPU ioctls to fail.
      
      By contrast, in the non-hotplug case the APIC is reset much later, when
      the vCPU is already initialized.
      
      As a quick and safe solution, move the qemu_init_vcpu() call back into
      the targets' realize functions.
      Reported-by: NChen Fan <chen.fan.fnst@cn.fujitsu.com>
      Acked-by: Igor Mammedov <imammedo@redhat.com> (for i386)
      Tested-by: Jia Liu <proljc@gmail.com> (for openrisc)
      Signed-off-by: NAndreas Färber <afaerber@suse.de>
      14a10fc3
  17. 27 7月, 2013 2 次提交
  18. 10 7月, 2013 1 次提交
  19. 28 6月, 2013 3 次提交
  20. 12 6月, 2013 2 次提交
  21. 11 6月, 2013 1 次提交
  22. 01 5月, 2013 4 次提交