From: Peter Xu <peterx@redhat.com>
To: Steve Sistare <steven.sistare@oracle.com>
Cc: qemu-devel@nongnu.org, "Juan Quintela" <quintela@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH V4 05/11] migration: preserve suspended for bg_migration
Date: Wed, 30 Aug 2023 12:35:06 -0400 [thread overview]
Message-ID: <ZO9vuqhUgaEkjPtV@x1n> (raw)
In-Reply-To: <1693333086-392798-6-git-send-email-steven.sistare@oracle.com>
On Tue, Aug 29, 2023 at 11:18:00AM -0700, Steve Sistare wrote:
> Do not wake a suspended guest during bg_migration.
>
> Signed-off-by: Steve Sistare <steven.sistare@oracle.com>
> ---
> migration/migration.c | 12 +++++-------
> softmmu/runstate.c | 1 +
> 2 files changed, 6 insertions(+), 7 deletions(-)
>
> diff --git a/migration/migration.c b/migration/migration.c
> index a9ecb66..303d5a6 100644
> --- a/migration/migration.c
> +++ b/migration/migration.c
> @@ -3064,7 +3064,9 @@ static void bg_migration_vm_start_bh(void *opaque)
> qemu_bh_delete(s->vm_start_bh);
> s->vm_start_bh = NULL;
>
> - vm_start();
> + if (!runstate_check(RUN_STATE_SUSPENDED)) {
> + vm_start();
> + }
> s->downtime = qemu_clock_get_ms(QEMU_CLOCK_REALTIME) - s->downtime_start;
> }
>
> @@ -3134,16 +3136,12 @@ static void *bg_migration_thread(void *opaque)
>
> qemu_mutex_lock_iothread();
>
> - /*
> - * If VM is currently in suspended state, then, to make a valid runstate
> - * transition in vm_stop_force_state() we need to wakeup it up.
> - */
> - qemu_system_wakeup_request(QEMU_WAKEUP_REASON_OTHER, NULL);
> s->vm_old_state = runstate_get();
>
> global_state_store();
> /* Forcibly stop VM before saving state of vCPUs and devices */
> - if (vm_stop_force_state(RUN_STATE_PAUSED)) {
> + if (!runstate_check(RUN_STATE_SUSPENDED) &&
> + vm_stop_force_state(RUN_STATE_PAUSED)) {
IIUC we need the vm_stop even for SUSPENDED? I think we need to make sure
all backends are stopped before we start wr-protect the guest pages, so
when wr-protect happens the guest pages should be in a consistent state.
I'd think it proper to juse reuse the helper you introduced in the previous
patches, but maybe you have a reason to not do so (I didn't see it
mentioned anywhere, though)?
> goto fail;
> }
> /*
> diff --git a/softmmu/runstate.c b/softmmu/runstate.c
> index 21d7407..4417527 100644
> --- a/softmmu/runstate.c
> +++ b/softmmu/runstate.c
> @@ -163,6 +163,7 @@ static const RunStateTransition runstate_transitions_def[] = {
> { RUN_STATE_SUSPENDED, RUN_STATE_FINISH_MIGRATE },
> { RUN_STATE_SUSPENDED, RUN_STATE_PRELAUNCH },
> { RUN_STATE_SUSPENDED, RUN_STATE_COLO},
> + { RUN_STATE_SUSPENDED, RUN_STATE_PAUSED },
>
> { RUN_STATE_WATCHDOG, RUN_STATE_RUNNING },
> { RUN_STATE_WATCHDOG, RUN_STATE_FINISH_MIGRATE },
> --
> 1.8.3.1
>
--
Peter Xu
next prev parent reply other threads:[~2023-08-30 16:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 18:17 [PATCH V4 00/11] fix migration of suspended runstate Steve Sistare
2023-08-29 18:17 ` [PATCH V4 01/11] cpus: pass runstate to vm_prepare_start Steve Sistare
2023-08-30 15:52 ` Peter Xu
2023-08-30 15:56 ` Steven Sistare
2023-08-29 18:17 ` [PATCH V4 02/11] migration: preserve suspended runstate Steve Sistare
2023-08-30 16:07 ` Peter Xu
2023-08-29 18:17 ` [PATCH V4 03/11] migration: add runstate function Steve Sistare
2023-08-30 16:11 ` Peter Xu
2023-08-29 18:17 ` [PATCH V4 04/11] migration: preserve suspended for snapshot Steve Sistare
2023-08-30 16:22 ` Peter Xu
2023-11-13 18:32 ` Steven Sistare
2023-08-29 18:18 ` [PATCH V4 05/11] migration: preserve suspended for bg_migration Steve Sistare
2023-08-30 16:35 ` Peter Xu [this message]
2023-11-13 18:32 ` Steven Sistare
2023-08-29 18:18 ` [PATCH V4 06/11] migration: preserve cpu ticks if suspended Steve Sistare
2023-08-30 16:47 ` Peter Xu
2023-09-07 15:50 ` Steven Sistare
2023-11-13 18:32 ` Steven Sistare
2023-08-29 18:18 ` [PATCH V4 07/11] tests/qtest: migration events Steve Sistare
2023-08-30 17:00 ` Peter Xu
2023-11-13 18:33 ` Steven Sistare
2023-11-13 19:20 ` Steven Sistare
2023-08-29 18:18 ` [PATCH V4 08/11] tests/qtest: option to suspend during migration Steve Sistare
2023-08-30 17:01 ` Peter Xu
2023-08-29 18:18 ` [PATCH V4 09/11] tests/qtest: precopy migration with suspend Steve Sistare
2023-08-29 18:18 ` [PATCH V4 10/11] tests/qtest: postcopy " Steve Sistare
2023-08-29 18:18 ` [PATCH V4 11/11] tests/qtest: background " Steve Sistare
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=ZO9vuqhUgaEkjPtV@x1n \
--to=peterx@redhat.com \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=steven.sistare@oracle.com \
--cc=thuth@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).