1. 18 Sep, 2014 1 commit
  2. 16 Sep, 2014 1 commit
  3. 09 Sep, 2014 2 commits
  4. 20 Aug, 2014 1 commit
    • Michael S. Tsirkin's avatar
      hostmem: set MPOL_MF_MOVE · 288d3322
      Michael S. Tsirkin authored
      When memory is allocated on a wrong node, MPOL_MF_STRICT
      doesn't move it - it just fails the allocation.
      A simple way to reproduce the failure is with mlock=on
      realtime feature.
      
      The code comment actually says: "ensure policy won't be ignored"
      so setting MPOL_MF_MOVE seems like a better way to do this.
      
      Cc: qemu-stable@nongnu.org
      Signed-off-by: default avatarMichael S. Tsirkin <mst@redhat.com>
      
      288d3322
  5. 18 Aug, 2014 1 commit
  6. 06 Aug, 2014 1 commit
    • Paolo Bonzini's avatar
      backends: Introduce chr-testdev · 5692399f
      Paolo Bonzini authored
      From: Paolo Bonzini <pbonzini@redhat.com>
      
      chr-testdev enables a virtio serial channel to be used for guest
      initiated qemu exits. hw/misc/debugexit already enables guest
      initiated qemu exits, but only for PC targets. chr-testdev supports
      any virtio-capable target. kvm-unit-tests/arm is already making use
      of this backend.
      
      Currently there is a single command implemented, "q".  It takes a
      (prefix) argument for the exit code, thus an exit is implemented by
      writing, e.g. "1q", to the virtio-serial port.
      
      It can be used as:
         $QEMU ... \
           -device virtio-serial-device \
           -device virtserialport,chardev=ctd -chardev testdev,id=ctd
      
      or, use:
         $QEMU ... \
           -device virtio-serial-device \
           -device virtconsole,chardev=ctd -chardev testdev,id=ctd
      
      to bind it to virtio-serial port0.
      Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: default avatarAndrew Jones <drjones@redhat.com>
      Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
      5692399f
  7. 24 Jun, 2014 1 commit
  8. 23 Jun, 2014 1 commit
  9. 19 Jun, 2014 7 commits
  10. 18 Jun, 2014 1 commit
  11. 08 May, 2014 1 commit
  12. 05 May, 2014 1 commit
    • Markus Armbruster's avatar
      qom: Clean up fragile use of error_is_set() in set() methods · 65cd9064
      Markus Armbruster authored
      Using error_is_set(ERRP) to find out whether a function failed is
      either wrong, fragile, or unnecessarily opaque.  It's wrong when ERRP
      may be null, because errors go undetected when it is.  It's fragile
      when proving ERRP non-null involves a non-local argument.  Else, it's
      unnecessarily opaque (see commit 84d18f06).
      
      I guess the error_is_set(errp) in the ObjectProperty set() methods are
      merely fragile right now, because I can't find a call chain that
      passes a null errp argument.
      
      Make the code more robust and more obviously correct: receive the
      error in a local variable, then propagate it through the parameter.
      Signed-off-by: default avatarMarkus Armbruster <armbru@redhat.com>
      Signed-off-by: default avatarAndreas Färber <afaerber@suse.de>
      65cd9064
  13. 24 Mar, 2014 1 commit
  14. 05 Mar, 2014 1 commit
    • Dave Airlie's avatar
      ui/sdl2 : initial port to SDL 2.0 (v2.0) · 47c03744
      Dave Airlie authored
      I've ported the SDL1.2 code over, and rewritten it to use the SDL2 interface.
      
      The biggest changes were in the input handling, where SDL2 has done a major
      overhaul, and I've had to include a generated translation file to get from
      SDL2 codes back to qemu compatible ones. I'm still not sure how the keyboard
      layout code works in qemu, so there may be further work if someone can point
      me a test case that works with SDL1.2 and doesn't with SDL2.
      
      Some SDL env vars we used to set are no longer used by SDL2,
      Windows, OSX support is untested,
      
      I don't think we can link to SDL1.2 and SDL2 at the same time, so I felt
      using --with-sdlabi=2.0 to select the new code should be fine, like how
      gtk does it.
      
      v1.1: fix keys in text console
      v1.2: fix shutdown, cleanups a bit of code, support ARGB cursor
      
      v2.0: merge the SDL multihead patch into this, g_new the number of consoles
      needed, wrap DCL inside per-console structure.
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      
      Fixes & improvements by kraxel:
       * baum build fix
       * remove text console logic
       * adapt to new input core
       * codestyle fixups
      Signed-off-by: default avatarGerd Hoffmann <kraxel@redhat.com>
      47c03744
  15. 28 Jan, 2014 2 commits
  16. 06 Jan, 2014 1 commit
  17. 21 Nov, 2013 4 commits
  18. 22 Aug, 2013 2 commits
  19. 17 Jun, 2013 1 commit
  20. 10 Jun, 2013 1 commit
    • Michael Roth's avatar
      qemu-char: don't issue CHR_EVENT_OPEN in a BH · bd5c51ee
      Michael Roth authored
      When CHR_EVENT_OPENED was initially added, it was CHR_EVENT_RESET,
      and it was issued as a bottom-half:
      
      86e94dea
      
      Which we basically used to print out a greeting/prompt for the
      monitor.
      
      AFAICT the only reason this was ever done in a BH was because in
      some cases we'd modify the chr_write handler for a new chardev
      backend *after* the site where we issued the reset (see:
      86e94d:qemu_chr_open_stdio())
      
      At some point this event was renamed to CHR_EVENT_OPENED, and we've
      maintained the use of this BH ever since.
      
      However, due to 9f939df9, we schedule
      the BH via g_idle_add(), which is causing events to sometimes be
      delivered after we've already begun processing data from backends,
      leading to:
      
       known bugs:
      
        QMP:
          session negotation resets with OPENED event, in some cases this
          is causing new sessions to get sporadically reset
      
       potential bugs:
      
        hw/usb/redirect.c:
          can_read handler checks for dev->parser != NULL, which may be
          true if CLOSED BH has not been executed yet. In the past, OPENED
          quiesced outstanding CLOSED events prior to us reading client
          data. If it's delayed, our check may allow reads to occur even
          though we haven't processed the OPENED event yet, and when we
          do finally get the OPENED event, our state may get reset.
      
        qtest.c:
          can begin session before OPENED event is processed, leading to
          a spurious reset of the system and irq_levels
      
        gdbstub.c:
          may start a gdb session prior to the machine being paused
      
      To fix these, let's just drop the BH.
      
      Since the initial reasoning for using it still applies to an extent,
      work around that by deferring the delivery of CHR_EVENT_OPENED until
      after the chardevs have been fully initialized, toward the end of
      qmp_chardev_add() (or some cases, qemu_chr_new_from_opts()). This
      defers delivery long enough that we can be assured a CharDriverState
      is fully initialized before CHR_EVENT_OPENED is sent.
      
      Also, rather than requiring each chardev to do an explicit open, do it
      automatically, and allow the small few who don't desire such behavior to
      suppress the OPENED-on-init behavior by setting a 'explicit_be_open'
      flag.
      
      We additionally add missing OPENED events for stdio backends on w32,
      which were previously not being issued, causing us to not recieve the
      banner and initial prompts for qmp/hmp.
      Reported-by: default avatarStefan Priebe <s.priebe@profihost.ag>
      Signed-off-by: default avatarMichael Roth <mdroth@linux.vnet.ibm.com>
      Message-id: 1370636393-21044-1-git-send-email-mdroth@linux.vnet.ibm.com
      Cc: qemu-stable@nongnu.org
      Signed-off-by: default avatarMichael Roth <mdroth@linux.vnet.ibm.com>
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      bd5c51ee
  21. 16 Apr, 2013 1 commit
  22. 15 Apr, 2013 2 commits
  23. 04 Apr, 2013 1 commit
  24. 02 Apr, 2013 1 commit
  25. 27 Mar, 2013 1 commit
  26. 13 Mar, 2013 2 commits