1. 01 11月, 2008 4 次提交
    • A
      CVE-2008-4539: fix a heap overflow in Cirrus emulation · 65d35a09
      aurel32 提交于
      The code in hw/cirrus_vga.c has changed a lot between CVE-2007-1320 has
      been announced and the patch has been applied. As a consequence it has
      wrongly applied and QEMU is still vulnerable to this bug if using VNC.
      
      (noticed by Jan Niehusmann)
      Signed-off-by: NAurelien Jarno <aurelien@aurel32.net>
      
      git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5587 c046a42c-6fe2-441c-8c8c-71466251a162
      65d35a09
    • A
      Malta & OMAP: add a name to char devices · 7cc0dd20
      aurel32 提交于
      (fixes regression introduced by r5575)
      Signed-off-by: NAurelien Jarno <aurelien@aurel32.net>
      
      git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5585 c046a42c-6fe2-441c-8c8c-71466251a162
      7cc0dd20
    • A
      Implement "info chardev" command. (Gerd Hoffmann) · 5ccfae10
      aliguori 提交于
      This patch makes qemu keep track of the character devices in use and
      implements a "info chardev" monitor command to print a list.
      
      qemu_chr_open() sticks the devices into a linked list now.  It got a new
      argument (label), so there is a name for each device.  It also assigns a
      filename to each character device.  By default it just copyes the
      filename passed in.  Individual drivers can fill in something else
      though.  qemu_chr_open_pty() sets the filename to name of the pseudo tty
      allocated.
      
      Output looks like this:
      
        (qemu) info chardev
        monitor: filename=unix:/tmp/run.sh-26827/monitor,server,nowait
        serial0: filename=unix:/tmp/run.sh-26827/console,server
        serial1: filename=pty:/dev/pts/5
        parallel0: filename=vc:640x480
      Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      
      
      
      git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5575 c046a42c-6fe2-441c-8c8c-71466251a162
      5ccfae10
    • A
      Make DMA bottom-half driven (v2) · 492c30af
      aliguori 提交于
      The current DMA routines are driven by a call in main_loop_wait() after every
      select.
      
      This patch converts the DMA code to be driven by a constantly rescheduled
      bottom half.  The advantage of using a scheduled bottom half is that we can
      stop scheduling the bottom half when there no DMA channels are runnable.  This
      means we can potentially detect this case and sleep longer in the main loop.
      
      The only two architectures implementing DMA_run() are cris and i386.  For cris,
      I converted it to a simple repeating bottom half.  I've only compile tested
      this as cris does not seem to work on a 64-bit host.  It should be functionally
      identical to the previous implementation so I expect it to work.
      
      For x86, I've made sure to only fire the DMA bottom half if there is a DMA
      channel that is runnable.  The effect of this is that unless you're using sb16
      or a floppy disk, the DMA bottom half never fires.
      
      You probably should test this malc.  My own benchmarks actually show slight
      improvement by it's possible the change in timing could affect your demos.
      
      Since v1, I've changed the code to use a BH instead of a timer.  cris at least
      seems to depend on faster than 10ms polling.
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      
      
      
      git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5573 c046a42c-6fe2-441c-8c8c-71466251a162
      492c30af
  2. 29 10月, 2008 1 次提交
  3. 28 10月, 2008 2 次提交
  4. 27 10月, 2008 1 次提交
  5. 26 10月, 2008 1 次提交
  6. 25 10月, 2008 5 次提交
  7. 24 10月, 2008 2 次提交
  8. 23 10月, 2008 2 次提交
  9. 17 10月, 2008 1 次提交
    • A
      scsi-generic: correct error management · 89c0f643
      aurel32 提交于
      this patch allows to fully use a tape device connected to qemu through
      the scsi-generic interface.
      
      Previous patch introduced tape SCSI commands management, this one
      improve error case management:
      
      - the SCSI controller command completion must be called with the status
      value, not the sense value. In the case of scsi-generic, the SCSI status
      is given by the field status of sg_io_hdr_t (the value is left shifted
      by one regarding status codes defined in /usr/include/scsi/scsi.h)
      
      - when a read is aborted due to a mark/EOF/EOD/EOM, the len reported to
      controller can be 0. LSI controller emulation doesn't know how to manage
      this. A workaround found is to call the completion routine with
      SCSI_REASON_DONE just after calling it with SCSI_REASON_DATA with len=0.
      
      This patch also manages correctly the block size of the tape device.
      
      This patch has been tested with a real tape device "HP C5683A", linux
      guest (debian etch) and tools like "mt", "tar" and "btape".
      
      Windows guest is not better supported than before...
      Signed-off-by: NLaurent Vivier <Laurent.Vivier@bull.net>
      Signed-off-by: NAurelien Jarno <aurelien@aurel32.net>
      
      git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5497 c046a42c-6fe2-441c-8c8c-71466251a162
      89c0f643
  10. 13 10月, 2008 3 次提交
  11. 12 10月, 2008 3 次提交
  12. 11 10月, 2008 2 次提交
  13. 09 10月, 2008 1 次提交
  14. 08 10月, 2008 2 次提交
  15. 06 10月, 2008 1 次提交
    • A
      Introduce v3 of savevm protocol · 9366f418
      aliguori 提交于
      The current savevm/loadvm protocol has some draw backs.  It does not support
      the ability to do progressive saving which means it cannot be used for live
      checkpointing or migration.  The sections sizes are 32-bit integers which
      means that it will not function when using more than 4GB of memory for a guest.
      It attempts to seek within the output file which means it cannot be streamed.
      The current protocol also is pretty lax about how it supports forward
      compatibility.  If a saved section version is greater than what the restore
      code support, the restore code generally treats the saved data as being in
      whatever version it supports.  This means that restoring a saved VM on an older
      version of QEMU will likely result in silent guest failure.
      
      This patch introduces a new version of the savevm protocol.  It has the
      following features:
      
       * Support for progressive save of sections (for live checkpoint/migration)
       * An asynchronous API for doing save
       * Support for interleaving multiple progressive save sections
         (for future support of memory hot-add/storage migration)
       * Fully streaming format
       * Strong section version checking
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      
      
      
      git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5434 c046a42c-6fe2-441c-8c8c-71466251a162
      9366f418
  16. 04 10月, 2008 5 次提交
  17. 03 10月, 2008 4 次提交