From: Markus Armbruster <armbru@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Chandan <csomani@redhat.com>,
qemu-devel@nongnu.org, Hanna Reitz <hreitz@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Eric Blake <eblake@redhat.com>,
"open list:Block layer core" <qemu-block@nongnu.org>
Subject: Re: [PATCH] block: enable stats-intervals for virtio-blk devs with -blockdev
Date: Tue, 07 Oct 2025 09:58:00 +0200 [thread overview]
Message-ID: <87ikgri1o7.fsf@pond.sub.org> (raw)
In-Reply-To: <aNvJGWApjqZTJFpV@redhat.com> (Kevin Wolf's message of "Tue, 30 Sep 2025 14:12:09 +0200")
Kevin Wolf <kwolf@redhat.com> writes:
> Am 30.09.2025 um 01:52 hat Chandan geschrieben:
>> This patch allows the stats-intervals.* flag to be used with
>> -blockdev. Stats collection is initialized for virtio-blk devices
>> at their time of creation. However, it is limited to just virtio-blk
>> devices for now.
>>
>> Signed-off-by: Chandan <csomani@redhat.com>
[...]
>> struct BlockBackendRootState {
>> diff --git a/qapi/block-core.json b/qapi/block-core.json
>> index dc6eb4ae23..dbb53296b1 100644
>> --- a/qapi/block-core.json
>> +++ b/qapi/block-core.json
>> @@ -4771,6 +4771,9 @@
>> # @force-share: force share all permission on added nodes. Requires
>> # read-only=true. (Since 2.10)
>> #
>> +# @stats-intervals: #optional list of intervals for collecting I/O
>> +# statistics, in seconds (default: none)
>
> #optional is not a marker that is used anywhere else.
Because it gets rendered like this:
* stats-intervals ([int], *optional*) -- #optional list of
intervals for collecting I/O statistics, in seconds (default:
none)
Drop it, please.
[...]
prev parent reply other threads:[~2025-10-07 7:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 23:52 [PATCH] block: enable stats-intervals for virtio-blk devs with -blockdev Chandan
2025-09-30 12:12 ` Kevin Wolf
2025-10-03 21:57 ` Chandan Somani
2025-10-07 7:58 ` Markus Armbruster [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=87ikgri1o7.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=csomani@redhat.com \
--cc=eblake@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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.