From: Markus Armbruster <armbru@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: "Markus Armbruster" <armbru@redhat.com>,
qemu-devel@nongnu.org, "Joao Martins" <joao.m.martins@oracle.com>,
"Cédric Le Goater" <clg@redhat.com>,
"Avihai Horon" <avihaih@nvidia.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Fabiano Rosas" <farosas@suse.de>,
"Prasad Pandit" <ppandit@redhat.com>,
"Alex Williamson" <alex@shazbot.org>,
"Kirti Wankhede" <kwankhede@nvidia.com>,
"Zhiyi Guo" <zhguo@redhat.com>,
"Maciej S . Szmigiero" <mail@maciej.szmigiero.name>,
"Juraj Marcin" <jmarcin@redhat.com>,
"Dr. David Alan Gilbert" <dave@treblig.org>
Subject: Re: [PATCH v2 14/16] migration/qapi: Introduce system-wise "remaining" reports
Date: Tue, 28 Apr 2026 21:02:52 +0200 [thread overview]
Message-ID: <87wlxqzz4z.fsf@pond.sub.org> (raw)
In-Reply-To: <afDRlNtG7wlmXchB@x1.local> (Peter Xu's message of "Tue, 28 Apr 2026 11:26:12 -0400")
Peter Xu <peterx@redhat.com> writes:
> On Sat, Apr 25, 2026 at 07:46:45AM +0200, Markus Armbruster wrote:
>> Peter Xu <peterx@redhat.com> writes:
[...]
>> > The complete new version of patch is here (I updated quite a few places on
>> > the commit message):
>> >
>> > https://gitlab.com/peterx/qemu/-/commit/86d973360890cecc564a4a5bcf9a01b9efde368a
>> >
>> > Thanks,
>>
>> I read the commit message. No surprises except
>>
>> It should be the same value as RAM's remaining report when VFIO is not
>> involved, and it should report more than that when VFIO is involved.
>>
>> One note is that this field will be an estimate and may not be sampled the
>> exact same time versus the RAM remaining section. So it may report
>> slightly different values even if only RAM is involved. The difference
>> shouldn't matter though to mgmt to make correct decisions.
>>
>> The second paragraph is new. The first paragraph says they "should be
>> the same", the second that they "may [be] slightly different".
>> Suboptimal.
>
> Yes, it is misleading, I overlooked that. :(
>
>>
>> Here's my try:
>>
>> It should be approximately the same value ...
>>
>> Only approximately, because this field will be ...
>>
>> It's just a commit message, though. Up to you.
>
> New version:
>
> When VFIO is not involved, the value reported in the new field should
> be approximately the same as reported in the "remaining" field of the
> RAM section. It is only an approximate value because the system-wide
> remaining data is a cached value, which gets frequently updated by
> migration core. OTOH, the RAM's remaining data is accurate.
>
> When VFIO is involved, the new value reported should normally be
> larger, because it will include the size of VFIO remaining data too.
Looks good to me, thanks!
>> QAPI schema
>> Acked-by: Markus Armbruster <armbru@redhat.com>
>
> Thanks, I will at least wait for 1-2 days if it still needs update.
next prev parent reply other threads:[~2026-04-28 19:03 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 20:20 [PATCH v2 00/16] migration/vfio: Fix a few issues on API misuse or statistic reports Peter Xu
2026-04-21 20:20 ` [PATCH v2 01/16] qemu-iotests: Add query-migrate test for dirty-bitmap Peter Xu
2026-04-22 8:08 ` Vladimir Sementsov-Ogievskiy
2026-04-24 14:50 ` Peter Xu
2026-04-21 20:20 ` [PATCH v2 02/16] migration: Fix low possibility downtime violation Peter Xu
2026-04-21 20:20 ` [PATCH v2 03/16] migration/qapi: Rename MigrationStats to MigrationRAMStats Peter Xu
2026-04-24 9:03 ` Markus Armbruster
2026-04-21 20:20 ` [PATCH v2 04/16] vfio/migration: Cache stop size in VFIOMigration Peter Xu
2026-04-21 20:20 ` [PATCH v2 05/16] migration/treewide: Merge @state_pending_{exact|estimate} APIs Peter Xu
2026-04-22 8:23 ` Vladimir Sementsov-Ogievskiy
2026-04-22 8:29 ` Vladimir Sementsov-Ogievskiy
2026-04-22 15:44 ` Peter Xu
2026-04-22 17:06 ` Vladimir Sementsov-Ogievskiy
2026-04-21 20:21 ` [PATCH v2 06/16] migration: Use the new save_query_pending() API directly Peter Xu
2026-04-21 20:21 ` [PATCH v2 07/16] migration: Introduce stopcopy_bytes in save_query_pending() Peter Xu
2026-04-22 13:16 ` Juraj Marcin
2026-04-23 15:05 ` Avihai Horon
2026-04-21 20:21 ` [PATCH v2 08/16] vfio/migration: Fix incorrect reporting for VFIO pending data Peter Xu
2026-04-21 20:21 ` [PATCH v2 09/16] migration: Move iteration counter out of RAM Peter Xu
2026-04-21 20:21 ` [PATCH v2 10/16] migration: Introduce a helper to return switchover bw estimate Peter Xu
2026-04-21 20:21 ` [PATCH v2 11/16] migration: Calculate expected downtime on demand Peter Xu
2026-04-21 20:21 ` [PATCH v2 12/16] migration: Fix calculation of expected_downtime to take VFIO info Peter Xu
2026-04-21 20:21 ` [PATCH v2 13/16] migration: Remember total dirty bytes in mig_stats Peter Xu
2026-04-22 13:18 ` Juraj Marcin
2026-04-21 20:21 ` [PATCH v2 14/16] migration/qapi: Introduce system-wise "remaining" reports Peter Xu
2026-04-24 7:17 ` Markus Armbruster
2026-04-24 15:15 ` Peter Xu
2026-04-25 5:46 ` Markus Armbruster
2026-04-28 15:26 ` Peter Xu
2026-04-28 19:02 ` Markus Armbruster [this message]
2026-04-21 20:21 ` [PATCH v2 15/16] migration/qapi: Update unit for avail-switchover-bandwidth Peter Xu
2026-04-24 7:18 ` Markus Armbruster
2026-04-21 20:21 ` [PATCH v2 16/16] vfio/migration: Add tracepoints for precopy/stopcopy query ioctls Peter Xu
2026-04-22 7:51 ` Cédric Le Goater
2026-04-22 7:52 ` Cédric Le Goater
2026-04-22 9:56 ` Cédric Le Goater
2026-04-23 15:10 ` Avihai Horon
2026-04-29 14:46 ` Avihai Horon
2026-04-29 15:43 ` Peter Xu
2026-04-29 18:03 ` Avihai Horon
2026-04-29 19:52 ` [PATCH v2 00/16] migration/vfio: Fix a few issues on API misuse or statistic reports Peter Xu
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=87wlxqzz4z.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=alex@shazbot.org \
--cc=avihaih@nvidia.com \
--cc=berrange@redhat.com \
--cc=clg@redhat.com \
--cc=dave@treblig.org \
--cc=farosas@suse.de \
--cc=jmarcin@redhat.com \
--cc=joao.m.martins@oracle.com \
--cc=kwankhede@nvidia.com \
--cc=mail@maciej.szmigiero.name \
--cc=peterx@redhat.com \
--cc=ppandit@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zhguo@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.