1. 08 May, 2012 1 commit
    • Luiz Capitulino's avatar
      runstate: introduce suspended state · ad02b96a
      Luiz Capitulino authored
      QEMU enters in this state when the guest suspends to ram (S3).
      This is important so that HMP users and QMP clients can know that
      the guest is suspended. QMP also has an event for this, but events
      are not reliable and are limited (ie. a client can connect to QEMU
      after the event has been emitted).
      Having a different state for S3 brings a new issue, though. Every
      device that doesn't run when the VM is stopped but wants to run
      when the VM is suspended has to check for RUN_STATE_SUSPENDED
      explicitly. This is the case for the keyboard and mouse devices,
      for example.
      Signed-off-by: default avatarLuiz Capitulino <lcapitulino@redhat.com>
      Acked-by: default avatarGerd Hoffmann <kraxel@redhat.com>
  2. 17 Feb, 2012 2 commits
  3. 27 Oct, 2011 1 commit
  4. 20 Aug, 2011 1 commit
  5. 23 Jul, 2011 1 commit
  6. 04 Jul, 2011 1 commit
  7. 09 Apr, 2011 1 commit
  8. 14 Jun, 2010 1 commit
  9. 01 Jun, 2010 1 commit
  10. 19 Mar, 2010 4 commits
    • Anthony Liguori's avatar
      Expose whether a mouse is an absolute device via QMP and the human monitor. · 1aaee43c
      Anthony Liguori authored
      For QMP, we just add an attribute which is backwards compatible.  For the human
      monitor, we add (absolute) to the end of the line.
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
    • Anthony Liguori's avatar
      Add notifier for mouse mode changes · 7e581fb3
      Anthony Liguori authored
      Right now, DisplayState clients rely on polling the mouse mode to determine
      when the device is changed to an absolute device.  Use a notification list to
      add an explicit notification.
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
    • Anthony Liguori's avatar
      Add kbd_mouse_has_absolute() · eb2e259d
      Anthony Liguori authored
      kbd_mouse_is_absolute tells us whether the current mouse handler is an absolute
      device.  kbd_mouse_has_absolute tells us whether we have any device that is
      capable of absolute input.
      This lets us tell a user that they have configured an absolute device but that
      the guest is not currently using it.
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
    • Anthony Liguori's avatar
      Rewrite mouse handlers to use QTAILQ and to have an activation function · 6fef28ee
      Anthony Liguori authored
      And convert usb-hid to use it (to avoid regression with bisection)
      Right now, when we do info mice and we've added a usb tablet, we don't see it
      until the guest starts using the tablet.  We implement this behavior in order
      to provide a means to delay registration of a mouse handler since we treat
      the last registered handler as the current handler.
      This is a usability problem though as we would like to give the user feedback
      that they've either 1) not added an absolute device 2) there is an absolute
      device but the guest isn't using it 3) we have an absolute device and it's
      By using QTAILQ and having an explicit activation function that moves the
      handler to the front of the queue, we can implement the same semantics as
      before with respect to automatically switching to usb tablet while providing
      the user with a whole lot more information.
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
  11. 09 Mar, 2010 1 commit
  12. 13 Jan, 2010 1 commit