1. 07 2月, 2011 6 次提交
  2. 31 1月, 2011 3 次提交
  3. 24 1月, 2011 4 次提交
  4. 10 1月, 2011 1 次提交
  5. 19 12月, 2010 1 次提交
    • B
      ahci: delete write-only variables (v2) · cdfe17df
      Blue Swirl 提交于
      Avoid these warnings with GCC 4.6.0:
      /src/qemu/hw/ide/ahci.c: In function 'ahci_reset_port':
      /src/qemu/hw/ide/ahci.c:810:14: error: variable 'tfd' set but not used [-Werror=unused-but-set-variable]
      /src/qemu/hw/ide/ahci.c: In function 'handle_cmd':
      /src/qemu/hw/ide/ahci.c:1103:19: error: variable 'pr' set but not used [-Werror=unused-but-set-variable]
      
      In the tfd variable case, fix the logic also.
      
      CC: Alexander Graf <agraf@suse.de>
      CC: Kevin Wolf <kwolf@redhat.com>
      Acked-by: NAlexander Graf <agraf@suse.de>
      Signed-off-by: NBlue Swirl <blauwirbel@gmail.com>
      cdfe17df
  6. 18 12月, 2010 2 次提交
  7. 17 12月, 2010 9 次提交
  8. 12 12月, 2010 5 次提交
  9. 11 12月, 2010 1 次提交
    • A
      Add endianness as io mem parameter · 2507c12a
      Alexander Graf 提交于
      As stated before, devices can be little, big or native endian. The
      target endianness is not of their concern, so we need to push things
      down a level.
      
      This patch adds a parameter to cpu_register_io_memory that allows a
      device to choose its endianness. For now, all devices simply choose
      native endian, because that's the same behavior as before.
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      Signed-off-by: NBlue Swirl <blauwirbel@gmail.com>
      2507c12a
  10. 29 11月, 2010 4 次提交
  11. 25 11月, 2010 1 次提交
  12. 22 11月, 2010 1 次提交
  13. 04 11月, 2010 1 次提交
  14. 22 10月, 2010 1 次提交
    • K
      ide: Handle flush failure · e2bcadad
      Kevin Wolf 提交于
      Instead of always assuming success for bdrv_aio_flush, actually do something
      with the error. This respects the werror option and accordingly ignores the
      error, reports it to the guest or stops the VM and retries after cont.
      
      Ignoring the error is trivial, obviously. For stopping the VM and retrying
      later old code can be reused, but we need to introduce a new status for "retry
      a flush". For reporting to the guest, fortunately the same action is required
      as for a failed read/write (status = DRDY | ERR, error = ABRT), so this code
      can be reused as well.
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      e2bcadad