1. 09 2月, 2012 2 次提交
  2. 04 2月, 2012 3 次提交
    • A
      qdev: remove baked in notion of aliases (v2) · 6acbe4c6
      Anthony Liguori 提交于
      Limit them to the device_add functionality.  Device aliases were a hack based
      on the fact that virtio was modeled the wrong way.  The mechanism for aliasing
      is very limited in that only one alias can exist for any device.
      
      We have to support it for the purposes of compatibility but we only need to
      support it in device_add so restrict it to that piece of code.
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      ---
      v1 -> v2
       - Use a table for aliases (Paolo)
      6acbe4c6
    • A
      qdev: kill off DeviceInfo · d307af79
      Anthony Liguori 提交于
      It is no longer used in the tree since everything is done natively through
      QEMU Object Model.
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      d307af79
    • A
      qdev: register all types natively through QEMU Object Model · 39bffca2
      Anthony Liguori 提交于
      This was done in a mostly automated fashion.  I did it in three steps and then
      rebased it into a single step which avoids repeatedly touching every file in
      the tree.
      
      The first step was a sed-based addition of the parent type to the subclass
      registration functions.
      
      The second step was another sed-based removal of subclass registration functions
      while also adding virtual functions from the base class into a class_init
      function as appropriate.
      
      Finally, a python script was used to convert the DeviceInfo structures and
      qdev_register_subclass functions to TypeInfo structures, class_init functions,
      and type_register_static calls.
      
      We are almost fully converted to QOM after this commit.
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      39bffca2
  3. 28 1月, 2012 6 次提交
  4. 26 1月, 2012 1 次提交
  5. 21 1月, 2012 1 次提交
  6. 21 12月, 2011 1 次提交
  7. 16 12月, 2011 1 次提交
  8. 15 12月, 2011 2 次提交
  9. 13 12月, 2011 1 次提交
  10. 06 12月, 2011 2 次提交
  11. 05 12月, 2011 1 次提交
  12. 25 11月, 2011 1 次提交
  13. 18 11月, 2011 1 次提交
  14. 11 11月, 2011 1 次提交
  15. 02 11月, 2011 1 次提交
  16. 29 10月, 2011 5 次提交
  17. 26 10月, 2011 1 次提交
  18. 11 10月, 2011 2 次提交
  19. 04 10月, 2011 1 次提交
    • L
      RunState: Rename enum values as generated by the QAPI · 0461d5a6
      Luiz Capitulino 提交于
      Next commit will convert the query-status command to use the
      RunState type as generated by the QAPI.
      
      In order to "transparently" replace the current enum by the QAPI
      one, we have to make some changes to some enum values.
      
      As the changes are simple renames, I'll do them in one shot. The
      changes are:
      
       - Rename the prefix from RSTATE_ to RUN_STATE_
       - RUN_STATE_SAVEVM to RUN_STATE_SAVE_VM
       - RUN_STATE_IN_MIGRATE to RUN_STATE_INMIGRATE
       - RUN_STATE_PANICKED to RUN_STATE_INTERNAL_ERROR
       - RUN_STATE_POST_MIGRATE to RUN_STATE_POSTMIGRATE
       - RUN_STATE_PRE_LAUNCH to RUN_STATE_PRELAUNCH
       - RUN_STATE_PRE_MIGRATE to RUN_STATE_PREMIGRATE
       - RUN_STATE_RESTORE to RUN_STATE_RESTORE_VM
       - RUN_STATE_PRE_MIGRATE to RUN_STATE_FINISH_MIGRATE
      Signed-off-by: NLuiz Capitulino <lcapitulino@redhat.com>
      0461d5a6
  20. 21 9月, 2011 1 次提交
  21. 20 9月, 2011 1 次提交
    • A
      AHCI Port Interrupt Enable register cleaning on soft reset · a26a13da
      Alexander Motin 提交于
      I've found that FreeBSD AHCI driver doesn't work with AHCI hardware
      emulation of QEMU 0.15.0. I believe the problem is on QEMU's side. As I
      see, it clears port's Interrupt Enable register each time when reset of
      any level happens. Is is reasonable for the global controller reset. It
      is probably not good, but acceptable for FreeBSD driver for the port
      hard reset. But it is IMO wrong for the device soft reset. None of real
      hardware I know behaves that way.
      Signed-off-by: NAlexander Motin <mav@FreeBSD.org>
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      a26a13da
  22. 19 9月, 2011 1 次提交
  23. 16 9月, 2011 1 次提交
    • L
      Replace the VMSTOP macros with a proper state type · 1dfb4dd9
      Luiz Capitulino 提交于
      Today, when notifying a VM state change with vm_state_notify(),
      we pass a VMSTOP macro as the 'reason' argument. This is not ideal
      because the VMSTOP macros tell why qemu stopped and not exactly
      what the current VM state is.
      
      One example to demonstrate this problem is that vm_start() calls
      vm_state_notify() with reason=0, which turns out to be VMSTOP_USER.
      
      This commit fixes that by replacing the VMSTOP macros with a proper
      state type called RunState.
      Signed-off-by: NLuiz Capitulino <lcapitulino@redhat.com>
      1dfb4dd9
  24. 12 9月, 2011 2 次提交