On 04/28/2017 02:53 PM, Max Reitz wrote: > On 27.04.2017 03:46, Eric Blake wrote: >> Mixing byte offset and sector allocation counts is a bit >> confusing. Also, reporting n/m sectors, where m decreases >> according to the remaining size of the file, isn't really >> adding any useful information. > > Since this map doesn't leave out any range in the image file -- not > really, no. :-) > >> Update the output to use >> byte counts, and adjust the affected tests (./check -qcow2 102, >> ./check -vpc 146).
My commit message is stale if test 179 gets committed first (although, as we mentioned earlier, I'm trying to split this series in two, which would delay the introduction of 179...) I still wonder if an even more concise representation is worth it; the resulting output lines are still quite long. We don't make any guarantees about qemu-io back-compat, so I may still tweak it further (but if I do, I'll drop R-b) I should probably also add a blurb to the commit message about how 'qemu-img map' and 'qemu-io map' are two different beasts. >> >> Signed-off-by: Eric Blake <ebl...@redhat.com> >> >> --- >> v10: rebase to updated test 179 >> v9: new patch >> --- >> qemu-io-cmds.c | 5 ++--- >> tests/qemu-iotests/102.out | 4 ++-- >> tests/qemu-iotests/146.out | 30 +++++++++++++++--------------- >> tests/qemu-iotests/179.out | 22 +++++++++++----------- >> 4 files changed, 30 insertions(+), 31 deletions(-) > > Reviewed-by: Max Reitz <mre...@redhat.com> > -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org
signature.asc
Description: OpenPGP digital signature
