From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>, Eric Blake <eblake@redhat.com>
Subject: [Qemu-devel] [PATCH 3/3] block: Remove unused BlockDeviceMapEntry
Date: Fri, 28 Jul 2017 15:45:52 +0200 [thread overview]
Message-ID: <1501249552-788-4-git-send-email-armbru@redhat.com> (raw)
In-Reply-To: <1501249552-788-1-git-send-email-armbru@redhat.com>
BlockDeviceMapEntry has never been used. It was added in commit
facd6e2 "so that it is published through the introspection mechanism."
What exactly introspecting types that aren't used for anything could
accomplish isn't clear. What "introspection mechanism" to use is also
nebulous. To the best of my knowledge, there has never been one that
covered this type. Certainly not query-qmp-schema, which includes
only types that are actually used in QMP.
Not being able to introspect BlockDeviceMapEntry hasn't bothered
anyone enough to complain in almost four years. Get rid of it.
Cc: Paolo Bonzini <pbonzini@redhat.com>
Cc: Eric Blake <eblake@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
---
qapi/block-core.json | 29 -----------------------------
1 file changed, 29 deletions(-)
diff --git a/qapi/block-core.json b/qapi/block-core.json
index 833c602..27790f3 100644
--- a/qapi/block-core.json
+++ b/qapi/block-core.json
@@ -383,35 +383,6 @@
{ 'enum': 'BlockDeviceIoStatus', 'data': [ 'ok', 'failed', 'nospace' ] }
##
-# @BlockDeviceMapEntry:
-#
-# Entry in the metadata map of the device (returned by "qemu-img map")
-#
-# @start: Offset in the image of the first byte described by this entry
-# (in bytes)
-#
-# @length: Length of the range described by this entry (in bytes)
-#
-# @depth: Number of layers (0 = top image, 1 = top image's backing file, etc.)
-# before reaching one for which the range is allocated. The value is
-# in the range 0 to the depth of the image chain - 1.
-#
-# @zero: the sectors in this range read as zeros
-#
-# @data: reading the image will actually read data from a file (in particular,
-# if @offset is present this means that the sectors are not simply
-# preallocated, but contain actual data in raw format)
-#
-# @offset: if present, the image file stores the data for this range in
-# raw format at the given offset.
-#
-# Since: 1.7
-##
-{ 'struct': 'BlockDeviceMapEntry',
- 'data': { 'start': 'int', 'length': 'int', 'depth': 'int', 'zero': 'bool',
- 'data': 'bool', '*offset': 'int' } }
-
-##
# @DirtyBitmapStatus:
#
# An enumeration of possible states that a dirty bitmap can report to the user.
--
2.7.5
next prev parent reply other threads:[~2017-07-28 13:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 13:45 [Qemu-devel] [PATCH 0/3] Don't QAPI without need Markus Armbruster
2017-07-28 13:45 ` [Qemu-devel] [PATCH 1/3] replay: Define ReplayMode without QAPI Markus Armbruster
2017-07-31 6:59 ` Pavel Dovgalyuk
2017-07-31 13:13 ` Markus Armbruster
2017-07-31 13:30 ` Pavel Dovgalyuk
2017-07-28 13:45 ` [Qemu-devel] [PATCH 2/3] COLO: Define COLOMode " Markus Armbruster
2017-07-28 17:17 ` Dr. David Alan Gilbert
2017-07-28 18:07 ` Eric Blake
2017-07-31 9:02 ` Markus Armbruster
2017-07-29 6:49 ` Hailiang Zhang
2017-07-28 13:45 ` Markus Armbruster [this message]
2017-07-28 18:10 ` [Qemu-devel] [PATCH 3/3] block: Remove unused BlockDeviceMapEntry Eric Blake
2017-12-15 13:13 ` Max Reitz
2017-07-28 18:10 ` [Qemu-devel] [PATCH 0/3] Don't QAPI without need Eric Blake
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=1501249552-788-4-git-send-email-armbru@redhat.com \
--to=armbru@redhat.com \
--cc=eblake@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).