All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-devel@nongnu.org, mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH 2/3] runstate: introduce suspended state
Date: Thu, 03 May 2012 09:56:52 +0200	[thread overview]
Message-ID: <4FA23A44.6040908@redhat.com> (raw)
In-Reply-To: <20120502153453.3ee5dc8e@doriath.home>

  Hi,

> I think that the question we have to answer is: apart from the keyboard
> and mouse, is there any device that wants to run while qemu is suspended?

pretty much anything which may wake up the guest.  The nics for example
for wake-on-lan.  I'm not sure whenever they care about the runstate at
all though.

Mouse and keyboard ignore events when the guest is stopped so if you
type into a vnc client for a stopped guest the events wouldn't get
queued up and cause unwanted effects when unpausing the guest.  When
suspended we want forward the events though so wakeup-by-keyboard works.

Not sure whenever we have simliar logic elsewhere (like stop queuing
network packets when the guest doesn't run).

cheers,
  Gerd

  reply	other threads:[~2012-05-03  7:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1335559216-13849-1-git-send-email-lcapitulino@redhat.com>
     [not found] ` <1335559216-13849-3-git-send-email-lcapitulino@redhat.com>
2012-05-02  7:08   ` [Qemu-devel] [PATCH 2/3] runstate: introduce suspended state Gerd Hoffmann
2012-05-02 18:34     ` Luiz Capitulino
2012-05-03  7:56       ` Gerd Hoffmann [this message]
2012-05-03 20:30         ` Luiz Capitulino
2012-05-04  8:50           ` Gerd Hoffmann
2012-05-04 13:33             ` Luiz Capitulino
2012-05-04 13:54               ` Gerd Hoffmann
2012-05-04 14:00                 ` Luiz Capitulino

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FA23A44.6040908@redhat.com \
    --to=kraxel@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.