From: Juan Quintela <quintela@redhat.com>
To: Keqian Zhu <zhukeqian1@huawei.com>
Cc: jfreimann@redhat.com, wanghaibin.wang@huawei.com,
qemu-arm@nongnu.org, qemu-devel@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PATCH] migration: Optimization about wait-unplug migration state
Date: Tue, 04 Feb 2020 10:14:24 +0100 [thread overview]
Message-ID: <87blqehfyn.fsf@secure.laptop> (raw)
In-Reply-To: <20200204050841.44453-1-zhukeqian1@huawei.com> (Keqian Zhu's message of "Tue, 4 Feb 2020 13:08:41 +0800")
Keqian Zhu <zhukeqian1@huawei.com> wrote:
> qemu_savevm_nr_failover_devices() is originally designed to
> get the number of failover devices, but it actually returns
> the number of "unplug-pending" failover devices now. Moreover,
> what drives migration state to wait-unplug should be the number
> of "unplug-pending" failover devices, not all failover devices.
>
> We can also notice that qemu_savevm_state_guest_unplug_pending()
> and qemu_savevm_nr_failover_devices() is equivalent almost (from
> the code view). So the latter is incorrect semantically and
> useless, just delete it.
>
> In the qemu_savevm_state_guest_unplug_pending(), once hit a
> unplug-pending failover device, then it can return true right
> now to save cpu time.
>
> Signed-off-by: Keqian Zhu <zhukeqian1@huawei.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
For my reading you are right:
- 1st function naming is not right
- 2nd function achieves exactly the same effect
I will wait until Jens says anything, but then I will queue it.
Thanks, Juan.
next prev parent reply other threads:[~2020-02-04 9:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 5:08 [PATCH] migration: Optimization about wait-unplug migration state Keqian Zhu
2020-02-04 9:14 ` Juan Quintela [this message]
2020-02-10 6:14 ` zhukeqian
2020-02-05 14:40 ` Jens Freimann
2020-02-10 6:14 ` zhukeqian
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=87blqehfyn.fsf@secure.laptop \
--to=quintela@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jfreimann@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wanghaibin.wang@huawei.com \
--cc=zhukeqian1@huawei.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 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).