From: Peter Xu <peterx@redhat.com>
To: Fabiano Rosas <farosas@suse.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] migration: Fix qmp_query_migrate mbps value
Date: Mon, 26 Feb 2024 09:44:58 +0800 [thread overview]
Message-ID: <ZdvtGqj6qmwDhHeN@x1n> (raw)
In-Reply-To: <87frxj9wy7.fsf@suse.de>
On Fri, Feb 23, 2024 at 09:39:12AM -0300, Fabiano Rosas wrote:
> I've been planning to merge migration_completion() and
> migration_iteration_finish(). It's too unintuitive to do the completion
> routine deep inside migration_iteration_run(). AFAICS those are all tail
> calls, so we could bring migration_completion() up into the
> migration_thread top level.
>
> So if you'll allow me I think I'll refrain from moving the state into
> migration_calculate_complete() for now.
Yep go ahead, I'll read the patches.
--
Peter Xu
prev parent reply other threads:[~2024-02-26 1:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 19:44 [PATCH] migration: Fix qmp_query_migrate mbps value Fabiano Rosas
2024-02-21 2:52 ` Peter Xu
2024-02-21 12:56 ` Fabiano Rosas
2024-02-22 9:40 ` Peter Xu
2024-02-22 13:29 ` Peter Xu
2024-02-22 13:49 ` Fabiano Rosas
2024-02-23 0:08 ` Peter Xu
2024-02-23 12:39 ` Fabiano Rosas
2024-02-26 1:44 ` Peter Xu [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=ZdvtGqj6qmwDhHeN@x1n \
--to=peterx@redhat.com \
--cc=farosas@suse.de \
--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).