All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hanna Reitz <hreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
	Eric Blake <eblake@redhat.com>,
	Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH v2 00/12] qemu-img info: Show protocol-level information
Date: Thu, 8 Dec 2022 13:24:01 +0100	[thread overview]
Message-ID: <7c2c9623-c865-91a3-01b7-0e7f90fde278@redhat.com> (raw)
In-Reply-To: <20220620162704.80987-1-hreitz@redhat.com>

On 20.06.22 18:26, Hanna Reitz wrote:
> Hi,
>
> This series is a v2 to:
>
> https://lists.nongnu.org/archive/html/qemu-block/2022-05/msg00042.html

Ping, it looks like this still applies (to the master branch and kevin’s 
block-next branch at least).

Hanna

> So the final state is that despite the QAPI changes, hopefully only the
> qemu-img info output changes, and it now prints every image node’s
> subgraph.  This results in an output like the following (for a qcow2
> image):
>
> image: test.qcow2
> file format: qcow2
> virtual size: 64 MiB (67108864 bytes)
> disk size: 196 KiB
> cluster_size: 65536
> Format specific information:
>      compat: 1.1
>      compression type: zlib
>      lazy refcounts: false
>      refcount bits: 16
>      corrupt: false
>      extended l2: false
> Child node '/file':
>      filename: test.qcow2
>      protocol type: file
>      file length: 192 KiB (197120 bytes)
>      disk size: 196 KiB
>      Format specific information:
>          extent size hint: 1048576



  parent reply	other threads:[~2022-12-08 12:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-20 16:26 [PATCH v2 00/12] qemu-img info: Show protocol-level information Hanna Reitz
2022-06-20 16:26 ` [PATCH v2 01/12] block: Improve empty format-specific info dump Hanna Reitz
2023-01-19 14:00   ` Kevin Wolf
2023-01-20 13:35     ` Hanna Czenczek
2023-01-20 14:08       ` Kevin Wolf
2022-06-20 16:26 ` [PATCH v2 02/12] block/file: Add file-specific image info Hanna Reitz
2023-01-27 23:00   ` Eric Blake
2022-06-20 16:26 ` [PATCH v2 03/12] block/vmdk: Change extent info type Hanna Reitz
2023-01-19 15:20   ` Kevin Wolf
2023-01-20 13:43     ` Hanna Czenczek
2023-01-27 23:06     ` Eric Blake
2023-01-30 10:56       ` Kevin Wolf
2022-06-20 16:26 ` [PATCH v2 04/12] block: Split BlockNodeInfo off of ImageInfo Hanna Reitz
2022-06-20 16:26 ` [PATCH v2 05/12] qemu-img: Use BlockNodeInfo Hanna Reitz
2022-06-20 16:26 ` [PATCH v2 06/12] block/qapi: Let bdrv_query_image_info() recurse Hanna Reitz
2022-06-20 16:26 ` [PATCH v2 07/12] block/qapi: Introduce BlockGraphInfo Hanna Reitz
2022-06-20 16:27 ` [PATCH v2 08/12] block/qapi: Add indentation to bdrv_node_info_dump() Hanna Reitz
2022-06-20 16:27 ` [PATCH v2 09/12] iotests: Filter child node information Hanna Reitz
2022-06-20 16:27 ` [PATCH v2 10/12] iotests/106, 214, 308: Read only one size line Hanna Reitz
2022-06-20 16:27 ` [PATCH v2 11/12] qemu-img: Let info print block graph Hanna Reitz
2022-06-20 16:27 ` [PATCH v2 12/12] qemu-img: Change info key names for protocol nodes Hanna Reitz
2022-12-08 12:24 ` Hanna Reitz [this message]
2023-01-19 20:12   ` [PATCH v2 00/12] qemu-img info: Show protocol-level information Kevin Wolf
2023-01-20 13:44     ` Hanna Czenczek

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=7c2c9623-c865-91a3-01b7-0e7f90fde278@redhat.com \
    --to=hreitz@redhat.com \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=kwolf@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 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.