All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: airlied@redhat.com, Anthony Liguori <aliguori@us.ibm.com>,
	Alon Levy <alevy@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] make screendump an async command
Date: Mon, 17 Jun 2013 09:54:30 -0400	[thread overview]
Message-ID: <20130617095430.0c54df50@redhat.com> (raw)
In-Reply-To: <51BEA782.7030201@redhat.com>

On Mon, 17 Jun 2013 08:06:58 +0200
Gerd Hoffmann <kraxel@redhat.com> wrote:

> Hmm, while thinking about it:  There is another screendump change in the
> pipeline: allow screen dumps from *any* device.  So, I think this is
> actually a very good reason to implement a new screendump command as I
> think we can kill two birds with one stone then:
> 
> First we can add a new parameter to specify the device we want dump
> from.  And second we are not bound to the behavior of the existing
> screendump command.  So we could simply send out a qmp event as
> completion (or error) notification.

That's how we agreed on doing async commands, and looks like a good
solution to me.

      parent reply	other threads:[~2013-06-17 13:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13 19:27 [Qemu-devel] [PATCH] make screendump an async command Alon Levy
2013-06-13 20:08 ` Paolo Bonzini
2013-06-13 20:35   ` Alon Levy
2013-06-14 11:18 ` Gerd Hoffmann
2013-06-14 18:02   ` Alon Levy
2013-06-14 18:07     ` Alon Levy
2013-06-14 18:21 ` Anthony Liguori
2013-06-14 23:55   ` Alon Levy
2013-06-17 13:41     ` Luiz Capitulino
2013-06-17  6:06   ` Gerd Hoffmann
2013-06-17  9:30     ` Alon Levy
2013-06-17 14:00       ` Gerd Hoffmann
2013-06-17 13:54     ` Luiz Capitulino [this message]

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=20130617095430.0c54df50@redhat.com \
    --to=lcapitulino@redhat.com \
    --cc=airlied@redhat.com \
    --cc=alevy@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=kraxel@redhat.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.