qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hanna Czenczek <hreitz@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org
Cc: eblake@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH 0/2] block: Expose block limits in monitor and qemu-img info
Date: Mon, 29 Sep 2025 16:02:33 +0200	[thread overview]
Message-ID: <cb615e7a-412f-469d-9fee-1f8621cc6aad@redhat.com> (raw)
In-Reply-To: <20250923163735.378254-1-kwolf@redhat.com>

On 23.09.25 18:37, Kevin Wolf wrote:
> This information can be useful both for debugging and for management
> tools trying to configure guest devices with the optimal limits
> (possibly across multiple hosts). There is no reason not to make it
> available, so just add it both in the monitor (QMP and HMP) and in
> 'qemu-img info'.
>
> Kevin Wolf (2):
>    block: Expose block limits for images in QMP
>    qemu-img info: Optionally show block limits

With or without the comment changes to patch 1:

Reviewed-by: Hanna Czenczek <hreitz@redhat.com>

(And I vote for keeping the paranthesized text in patch 2.)



      parent reply	other threads:[~2025-09-29 14:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-23 16:37 [PATCH 0/2] block: Expose block limits in monitor and qemu-img info Kevin Wolf
2025-09-23 16:37 ` [PATCH 1/2] block: Expose block limits for images in QMP Kevin Wolf
2025-09-23 18:03   ` Eric Blake
2025-09-24  6:10   ` Markus Armbruster
2025-09-24  9:05     ` Kevin Wolf
2025-09-24 10:43       ` Markus Armbruster
2025-09-23 16:37 ` [PATCH 2/2] qemu-img info: Optionally show block limits Kevin Wolf
2025-09-23 18:09   ` Eric Blake
2025-09-24  8:28     ` Kevin Wolf
2025-09-29 14:02 ` Hanna Czenczek [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=cb615e7a-412f-469d-9fee-1f8621cc6aad@redhat.com \
    --to=hreitz@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 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).