Skip to content

Q
qemu

openeuler / qemu

通知 10
Star 0
Fork 0
Q
qemu
切换分支/标签
  1. 29 9月, 2012 1 次提交
  3. 10 2月, 2012 1 次提交
  5. 21 1月, 2012 1 次提交
  7. 13 12月, 2011 1 次提交
  9. 05 12月, 2011 1 次提交
  11. 02 11月, 2011 1 次提交
  13. 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
  15. 12 9月, 2011 1 次提交
  17. 08 8月, 2011 1 次提交
  19. 15 6月, 2011 4 次提交
  21. 18 5月, 2011 2 次提交
  23. 16 4月, 2011 1 次提交
  25. 24 1月, 2011 2 次提交
  27. 17 12月, 2010 1 次提交
  29. 29 11月, 2010 2 次提交
  31. 25 11月, 2010 1 次提交
  33. 03 8月, 2010 1 次提交
    • A
      ide: Avoid canceling IDE DMA · 953844d1
      由 Andrea Arcangeli 提交于 
      The reason for not actually canceling the I/O is because with
virtualization and lots of VM running, a guest fs may mistake a
overload of the host, as an IDE timeout. So rather than canceling the
I/O, it's safer to wait I/O completion and simulate that the I/O has
completed just before the io cancellation was requested by the
guest. This way if ntfs or an app writes data without checking for
-EIO retval, and it thinks the write has succeeded, it's less likely
to run into troubles. Similar issues for reads.

Furthermore because the DMA operation is splitted into many synchronous
aio_read/write if there's more than one entry in the SG table, without this
patch the DMA would be cancelled in the middle, something we've no idea if it
happens on real hardware too or not. Overall this seems a great risk for zero
gain.

This approach is sure safer than previous code given we can't pretend all guest
fs code out there to check for errors and reply the DMA if it was completed
partially, given a timeout would never materialize on a real harddisk unless
there are defective blocks (and defective blocks are practically only an issue
for reads never for writes in any recent hardware as writing to blocks is the
way to fix them) or the harddisk breaks as a whole.
Signed-off-by: NIzik Eidus <ieidus@redhat.com>
Signed-off-by: NAndrea Arcangeli <aarcange@redhat.com>
Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      953844d1
  35. 27 7月, 2010 2 次提交
  37. 27 1月, 2010 1 次提交
    • M
      ide save/restore current transfer fields · 42ee76fe
      由 Marcelo Tosatti 提交于 
      If migration takes place between write of the bmdma address register and
write of the command register (to initiate DMA), the destination will
not properly start the DMA op, hanging the guest:

ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: cmd c8/00:16:41:00:00/00:00:00:00:00/e0 tag 0 dma 11264 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata1.00: status: { DRDY }

Fix by sending current transfer information in the migration data.

We need to update ide version to 4 for this to work.  As we don't
have subsectios, we need to chain the update increase until
vmstate_ide_pci (quintela)
Signed-off-by: NMarcelo Tosatti <mtosatti@redhat.com>
Signed-off-by: NJuan Quintela <quintela@redhat.com>
Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      42ee76fe
  39. 28 10月, 2009 1 次提交
  41. 12 10月, 2009 5 次提交
  43. 07 10月, 2009 1 次提交
    • M
      New qdev_init_nofail() · e23a1b33
      由 Markus Armbruster 提交于 
      Like qdev_init(), but terminate program via hw_error() instead of
returning an error value.

Use it instead of qdev_init() where terminating the program on failure
is okay, either because it's during machine construction, or because
we know that failure can't happen.

Because relying in the latter is somewhat unclean, and the former is
not always obvious, it would be nice to go back to qdev_init() in the
not-so-obvious cases, only with proper error handling.  I'm leaving
that for another day, because it involves making sure that error
values are properly checked by all callers.

Patchworks-ID: 35168
Signed-off-by: NMarkus Armbruster <armbru@redhat.com>
Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      e23a1b33
  45. 05 10月, 2009 2 次提交
  47. 16 9月, 2009 2 次提交
  49. 04 9月, 2009 2 次提交
  51. 28 8月, 2009 1 次提交