From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Lidong Chen <jemmy858585@gmail.com>
Cc: quintela@redhat.com, qemu-devel@nongnu.org,
Lidong Chen <lidongchen@tencent.com>
Subject: Re: [Qemu-devel] [PATCH] migration: release MigrationIncomingState in migration_object_finalize
Date: Thu, 5 Jul 2018 12:05:26 +0100 [thread overview]
Message-ID: <20180705110525.GL2538@work-vm> (raw)
In-Reply-To: <1528106113-32692-1-git-send-email-lidongchen@tencent.com>
* Lidong Chen (jemmy858585@gmail.com) wrote:
> Qemu initialize the MigrationIncomingState structure in migration_object_init,
> but not release it. this patch release it in migration_object_finalize.
>
> Signed-off-by: Lidong Chen <lidongchen@tencent.com>
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> ---
> migration/migration.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/migration/migration.c b/migration/migration.c
> index 05aec2c..e009a05 100644
> --- a/migration/migration.c
> +++ b/migration/migration.c
> @@ -156,6 +156,13 @@ void migration_object_init(void)
> void migration_object_finalize(void)
> {
> object_unref(OBJECT(current_migration));
> +
> + qemu_sem_destroy(¤t_incoming->postcopy_pause_sem_fault);
> + qemu_sem_destroy(¤t_incoming->postcopy_pause_sem_dst);
> + qemu_event_destroy(¤t_incoming->main_thread_load_event);
> + qemu_mutex_destroy(¤t_incoming->rp_mutex);
> + g_array_free(current_incoming->postcopy_remote_fds, true);
> + g_free(current_incoming);
> }
>
> /* For outgoing */
> --
> 1.8.3.1
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2018-07-05 11:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 9:55 [Qemu-devel] [PATCH] migration: release MigrationIncomingState in migration_object_finalize Lidong Chen
2018-07-05 11:05 ` Dr. David Alan Gilbert [this message]
2018-07-06 9:53 ` Dr. David Alan Gilbert
2018-07-06 10:41 ` Dr. David Alan Gilbert
2018-07-12 4:08 ` 858585 jemmy
2018-07-17 14:55 ` 858585 jemmy
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=20180705110525.GL2538@work-vm \
--to=dgilbert@redhat.com \
--cc=jemmy858585@gmail.com \
--cc=lidongchen@tencent.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).