From: Wei Yang <richardw.yang@linux.intel.com>
To: quintela@redhat.com, dgilbert@redhat.com
Cc: qemu-devel@nongnu.org, Wei Yang <richardw.yang@linux.intel.com>
Subject: [PATCH 0/3] migration/postcopy: replace have_listen_thread check with PostcopyState check
Date: Sun, 6 Oct 2019 08:02:46 +0800 [thread overview]
Message-ID: <20191006000249.29926-1-richardw.yang@linux.intel.com> (raw)
have_listen_thread is used to be a indication of whether postcopy thread is
running. Since we use PostcopyState to record state and the postcopy thread
only runs when postcopy_is_running(), we can leverage the PostcopyState to
replace the meaning of have_listen_thread.
To do so, two preparation cleanup is included.
Wei Yang (3):
migration/postcopy: mis->have_listen_thread check will never be
touched
migration/postcopy: postpone setting PostcopyState to END
migration/postcopy: replace have_listen_thread check with
PostcopyState check
migration/migration.h | 1 -
migration/postcopy-ram.c | 2 --
migration/ram.c | 2 +-
migration/ram.h | 1 +
migration/savevm.c | 11 +++--------
5 files changed, 5 insertions(+), 12 deletions(-)
--
2.17.1
next reply other threads:[~2019-10-06 0:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-06 0:02 Wei Yang [this message]
2019-10-06 0:02 ` [PATCH 1/3] migration/postcopy: mis->have_listen_thread check will never be touched Wei Yang
2019-10-08 18:47 ` Dr. David Alan Gilbert
2019-10-06 0:02 ` [PATCH 2/3] migration/postcopy: postpone setting PostcopyState to END Wei Yang
2019-10-08 19:06 ` Dr. David Alan Gilbert
2019-10-06 0:02 ` [PATCH 3/3] migration/postcopy: replace have_listen_thread check with PostcopyState check Wei Yang
2019-10-08 19:15 ` Dr. David Alan Gilbert
2019-10-09 1:37 ` Wei Yang
2019-10-09 10:17 ` Dr. David Alan Gilbert
2019-10-10 1:21 ` Wei Yang
2019-10-11 13:58 ` [PATCH 0/3] " Dr. David Alan Gilbert
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=20191006000249.29926-1-richardw.yang@linux.intel.com \
--to=richardw.yang@linux.intel.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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 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).