From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org, quintela@redhat.com, peterx@redhat.com
Subject: Re: [Qemu-devel] possible ahci/migrate fix
Date: Wed, 27 Feb 2019 16:46:37 +0000 [thread overview]
Message-ID: <87imx5kwlu.fsf@zen.linaroharston> (raw)
In-Reply-To: <20190227121052.GD2602@work-vm>
Dr. David Alan Gilbert <dgilbert@redhat.com> writes:
> Hi Alex,
> Can you see if the attached patch fixes the ahci/migrate failure you
> see; it won't fail for me however mean I am to it.
over 2000 iterations without issue, commit before crashed within 30
Tested-by: Alex Bennée <alex.bennee@linaro.org>
How quickly can we get this merged?
>
>
> From f4c327d14d656d1c0f0e694d0efc6165493416f0 Mon Sep 17 00:00:00 2001
> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> Date: Wed, 27 Feb 2019 12:04:37 +0000
> Subject: [PATCH] migration: Cleanup during exit
>
> Currently we cleanup the migration object as we exit main after the
> main_loop finishes; however if there's a migration running things
> get messy and we can end up with the migration thread still trying
> to access freed structures.
>
> We now take a ref to the object around the migration thread itself,
> so the act of dropping the ref during exit doesn't cause us to lose
> the state until the thread quits.
>
> Cancelling the migration during migration also tries to get the thread
> to quit.
>
> We do this a bit earlier; so hopefully migration gets out of the way
> before all the devices etc are freed.
>
> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> ---
> migration/migration.c | 8 ++++++++
> vl.c | 7 ++++++-
> 2 files changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/migration/migration.c b/migration/migration.c
> index e44f77af02..f612313d09 100644
> --- a/migration/migration.c
> +++ b/migration/migration.c
> @@ -126,6 +126,7 @@ static bool migration_object_check(MigrationState *ms, Error **errp);
> static int migration_maybe_pause(MigrationState *s,
> int *current_active_state,
> int new_state);
> +static void migrate_fd_cancel(MigrationState *s);
>
> void migration_object_init(void)
> {
> @@ -169,6 +170,11 @@ void migration_object_init(void)
>
> void migration_object_finalize(void)
> {
> + /*
> + * Cancel the current migration - that will (eventually)
> + * stop the migration using this structure
> + */
> + migrate_fd_cancel(current_migration);
> object_unref(OBJECT(current_migration));
> }
>
> @@ -3134,6 +3140,7 @@ static void *migration_thread(void *opaque)
>
> rcu_register_thread();
>
> + object_ref(OBJECT(s));
> s->iteration_start_time = qemu_clock_get_ms(QEMU_CLOCK_REALTIME);
>
> qemu_savevm_state_header(s->to_dst_file);
> @@ -3230,6 +3237,7 @@ static void *migration_thread(void *opaque)
>
> trace_migration_thread_after_loop();
> migration_iteration_finish(s);
> + object_unref(OBJECT(s));
> rcu_unregister_thread();
> return NULL;
> }
> diff --git a/vl.c b/vl.c
> index 2f340686a7..c1920165f3 100644
> --- a/vl.c
> +++ b/vl.c
> @@ -4579,6 +4579,12 @@ int main(int argc, char **argv, char **envp)
>
> gdbserver_cleanup();
>
> + /*
> + * cleaning up the migration object cancels any existing migration
> + * try to do this early so that it also stops using devices.
> + */
> + migration_object_finalize();
> +
> /* No more vcpu or device emulation activity beyond this point */
> vm_shutdown();
>
> @@ -4594,7 +4600,6 @@ int main(int argc, char **argv, char **envp)
> monitor_cleanup();
> qemu_chr_cleanup();
> user_creatable_cleanup();
> - migration_object_finalize();
> /* TODO: unref root container, check all devices are ok */
>
> return 0;
> --
> 2.20.1
--
Alex Bennée
next prev parent reply other threads:[~2019-02-27 16:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 12:10 [Qemu-devel] possible ahci/migrate fix Dr. David Alan Gilbert
2019-02-27 12:41 ` Juan Quintela
2019-02-27 13:16 ` Dr. David Alan Gilbert
2019-02-27 16:46 ` Alex Bennée [this message]
2019-02-27 16:51 ` Dr. David Alan Gilbert
2019-02-27 20:30 ` Juan Quintela
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=87imx5kwlu.fsf@zen.linaroharston \
--to=alex.bennee@linaro.org \
--cc=dgilbert@redhat.com \
--cc=peterx@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).