From: Luiz Capitulino <lcapitulino@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kwolf@redhat.com, eblake@redhat.com, qemu-devel@nongnu.org,
armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/4]: QMP: add BLOCK_MEDIUM_EJECT event
Date: Fri, 17 Feb 2012 09:58:59 -0200 [thread overview]
Message-ID: <20120217095859.5e3f213d@doriath.home> (raw)
In-Reply-To: <4F3E30B1.9000101@redhat.com>
On Fri, 17 Feb 2012 11:49:21 +0100
Paolo Bonzini <pbonzini@redhat.com> wrote:
> On 02/15/2012 07:42 PM, Luiz Capitulino wrote:
> > There's been one non-rfc patch and one or two rfc ones. This is v2 of the
> > non-rfc one.
> >
> > I think this version does what Kevin and Markus were asking: the event is
> > emitted whenever the tray moves, be it the guest or HMP/QMP commands.
> >
> > In a previous email I said that I'd be reviving an old series that breaks the
> > eject and change commands into multiple tray commands (tray-open/close,
> > medium-insert/remove etc), but that's not so trivial anymore as the tray state
> > moved to device models (still possible of course, but requires a bit more
> > work). So I decided to do it the way patch 4/4 does it.
> >
> > QMP/qmp-events.txt | 17 ++++++++++
> > block.c | 84 +++++++++++++++++++++++++++++++++------------------
> > block.h | 8 ++--
> > block/raw-posix.c | 6 ++--
> > block/raw.c | 4 +-
> > block_int.h | 2 +-
> > hw/ide/atapi.c | 2 +-
> > hw/ide/core.c | 8 ++--
> > hw/scsi-disk.c | 8 ++--
> > hw/virtio-blk.c | 6 ++--
> > monitor.c | 3 ++
> > monitor.h | 1 +
> > 12 files changed, 97 insertions(+), 52 deletions(-)
>
> We can seek perfection, but we can also do that incrementally. We're
> discussing the code more than the actual behavior, so
>
> Acked-by: Paolo Bonzini <pbonzini@redhat.com>
I'll submit v3 with a few renames and the change proposed by Markus, which is
not to call bdrv_eject() in the device models if the tray didn't move.
prev parent reply other threads:[~2012-02-17 11:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 18:42 [Qemu-devel] [PATCH v2 0/4]: QMP: add BLOCK_MEDIUM_EJECT event Luiz Capitulino
2012-02-15 18:42 ` [Qemu-devel] [PATCH 1/4] block: Rename bdrv_mon_event() & BlockMonEventAction Luiz Capitulino
2012-02-15 18:42 ` [Qemu-devel] [PATCH 2/4] block: bdrv_eject(): Make eject_flag a real bool Luiz Capitulino
2012-02-15 18:42 ` [Qemu-devel] [PATCH 3/4] block: bdrv_eject(): Add tray_changed parameter Luiz Capitulino
2012-02-15 18:42 ` [Qemu-devel] [PATCH 4/4] qmp: add BLOCK_MEDIUM_EJECT event Luiz Capitulino
2012-02-16 9:25 ` Markus Armbruster
2012-02-16 13:14 ` Luiz Capitulino
2012-02-16 13:19 ` Luiz Capitulino
2012-02-16 13:31 ` Kevin Wolf
2012-02-16 14:10 ` Luiz Capitulino
2012-02-17 10:32 ` Paolo Bonzini
2012-02-17 11:03 ` Kevin Wolf
2012-02-17 11:48 ` Markus Armbruster
2012-02-17 12:12 ` Kevin Wolf
2012-02-17 12:43 ` Markus Armbruster
2012-02-16 18:30 ` Markus Armbruster
2012-02-16 19:08 ` Luiz Capitulino
2012-02-17 9:53 ` Kevin Wolf
2012-02-17 10:48 ` Paolo Bonzini
2012-02-17 11:50 ` Markus Armbruster
2012-02-17 11:44 ` Markus Armbruster
2012-02-17 11:56 ` Luiz Capitulino
2012-02-17 10:45 ` Paolo Bonzini
2012-02-17 11:57 ` Markus Armbruster
2012-02-17 10:49 ` [Qemu-devel] [PATCH v2 0/4]: QMP: " Paolo Bonzini
2012-02-17 11:58 ` 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=20120217095859.5e3f213d@doriath.home \
--to=lcapitulino@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).