qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, mreitz@redhat.com, eblake@redhat.com,
	qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/3] block: Extend QMP events for anonymous BlockBackends
Date: Wed,  5 Oct 2016 11:26:10 +0200	[thread overview]
Message-ID: <1475659573-1664-1-git-send-email-kwolf@redhat.com> (raw)

We have two QMP events that include only a BlockBackend name and that are
therefore useless with anonymous BBs. This series adds a node-name/qdev ID to
them.

Kevin Wolf (3):
  block: Add node name to BLOCK_IO_ERROR event
  block-backend: Remember if attached device is non-qdev
  block: Add qdev ID to DEVICE_TRAY_MOVED

 block.c                        |  7 -----
 block/block-backend.c          | 64 +++++++++++++++++++++++++++++++++++-------
 docs/qmp-commands.txt          |  3 ++
 docs/qmp-events.txt            | 12 ++++++--
 hw/block/xen_disk.c            |  2 +-
 include/sysemu/block-backend.h |  4 +--
 qapi/block-core.json           |  8 ++++--
 qapi/block.json                |  8 ++++--
 8 files changed, 82 insertions(+), 26 deletions(-)

-- 
1.8.3.1

             reply	other threads:[~2016-10-05  9:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-05  9:26 Kevin Wolf [this message]
2016-10-05  9:26 ` [Qemu-devel] [PATCH 1/3] block: Add node name to BLOCK_IO_ERROR event Kevin Wolf
2016-10-05 17:48   ` Max Reitz
2016-10-05  9:26 ` [Qemu-devel] [PATCH 2/3] block-backend: Remember if attached device is non-qdev Kevin Wolf
2016-10-05 18:01   ` Max Reitz
2016-10-05 19:11     ` Eric Blake
2016-10-06 11:29     ` Kevin Wolf
2016-10-05  9:26 ` [Qemu-devel] [PATCH 3/3] block: Add qdev ID to DEVICE_TRAY_MOVED Kevin Wolf
2016-10-05 18:21   ` Max Reitz

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=1475659573-1664-1-git-send-email-kwolf@redhat.com \
    --to=kwolf@redhat.com \
    --cc=eblake@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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).