1. 03 12月, 2009 3 次提交
  2. 09 11月, 2009 2 次提交
  3. 28 8月, 2009 1 次提交
    • G
      qdev: add return value to init() callbacks. · 81a322d4
      Gerd Hoffmann 提交于
      Sorry folks, but it has to be.  One more of these invasive qdev patches.
      
      We have a serious design bug in the qdev interface:  device init
      callbacks can't signal failure because the init() callback has no
      return value.  This patch fixes it.
      
      We have already one case in-tree where this is needed:
      Try -device virtio-blk-pci (without drive= specified) and watch qemu
      segfault.  This patch fixes it.
      
      With usb+scsi being converted to qdev we'll get more devices where the
      init callback can fail for various reasons.
      Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      81a322d4
  4. 22 8月, 2009 1 次提交
  5. 17 7月, 2009 1 次提交
  6. 11 7月, 2009 1 次提交
  7. 09 7月, 2009 1 次提交
  8. 30 6月, 2009 1 次提交
  9. 20 6月, 2009 1 次提交
  10. 17 6月, 2009 1 次提交
  11. 22 5月, 2009 1 次提交
    • J
      Introduce reset notifier order · 8217606e
      Jan Kiszka 提交于
      Add the parameter 'order' to qemu_register_reset and sort callbacks on
      registration. On system reset, callbacks with lower order will be
      invoked before those with higher order. Update all existing users to the
      standard order 0.
      
      Note: At least for x86, the existing users seem to assume that handlers
      are called in their registration order. Therefore, the patch preserves
      this property. If someone feels bored, (s)he could try to identify this
      dependency and express it properly on callback registration.
      Signed-off-by: NJan Kiszka <jan.kiszka@siemens.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      8217606e
  12. 14 5月, 2009 1 次提交
  13. 12 5月, 2009 1 次提交
  14. 04 5月, 2009 1 次提交
  15. 02 2月, 2009 1 次提交
  16. 26 1月, 2009 1 次提交
  17. 23 12月, 2008 1 次提交
  18. 04 12月, 2008 1 次提交
  19. 22 6月, 2008 1 次提交
  20. 08 6月, 2008 1 次提交
    • M
      Do not scare users with ominous error messages from AUD_open* · 2c44375d
      malc 提交于
      Apparently Windows Server 2003 sets the frequency for either mc or pi
      voice to zero, which in turn triggers a call to audio_bug from this
      chain:
      
      open_voice -> AUD_open_in -> audio_bug (audio_validate_settings):
      
      A bug was just triggered in AUD_open_in
      ...
      Context:
      audio: frequency=0 nchannels=2 fmt=S16 endianness=little
      
      But since no attempt by the said OS is made to actually use the voice
      with zero frequency this can be considered normal behavior.
      
      Hence if zero freqency situation is encountered - close current voice,
      and make noises if the guest tries to use it.
      
      Reported by simon@...ve
      
      
      git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@4694 c046a42c-6fe2-441c-8c8c-71466251a162
      2c44375d
  21. 14 1月, 2008 1 次提交