qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	"Daniel P . Berrange" <berrange@redhat.com>,
	Stefan Hajnoczi <shajnocz@redhat.com>,
	Fam Zheng <famz@redhat.com>,
	"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
	peterx@redhat.com
Subject: [Qemu-devel] [PATCH 3/3] iothread: delay the context release to finalize
Date: Fri, 22 Sep 2017 16:56:12 +0800	[thread overview]
Message-ID: <1506070572-7549-4-git-send-email-peterx@redhat.com> (raw)
In-Reply-To: <1506070572-7549-1-git-send-email-peterx@redhat.com>

When gcontext is used with iothread, the context will be destroyed
during iothread_stop().  That's not good since sometimes we would like
to keep the resources until iothread is destroyed, but we may want to
stop the thread before that point.

Delay the destruction of gcontext to iothread finalize.  Then we can do:

  iothread_stop(thread);
  some_cleanup_on_resources();
  iothread_destroy(thread);

Signed-off-by: Peter Xu <peterx@redhat.com>
---
 iothread.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/iothread.c b/iothread.c
index 894756b..b95369b 100644
--- a/iothread.c
+++ b/iothread.c
@@ -71,8 +71,6 @@ static void *iothread_run(void *opaque)
             g_main_loop_unref(loop);
 
             g_main_context_pop_thread_default(iothread->worker_context);
-            g_main_context_unref(iothread->worker_context);
-            iothread->worker_context = NULL;
         }
     }
 
@@ -117,6 +115,10 @@ static void iothread_instance_finalize(Object *obj)
     IOThread *iothread = IOTHREAD(obj);
 
     iothread_stop(iothread);
+    if (iothread->worker_context) {
+        g_main_context_unref(iothread->worker_context);
+        iothread->worker_context = NULL;
+    }
     qemu_cond_destroy(&iothread->init_done_cond);
     qemu_mutex_destroy(&iothread->init_done_lock);
     if (!iothread->ctx) {
-- 
2.7.4

  parent reply	other threads:[~2017-09-22  8:56 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-22  8:56 [Qemu-devel] [PATCH 0/3] iothread: allow to create internal iothreads Peter Xu
2017-09-22  8:56 ` [Qemu-devel] [PATCH 1/3] iothread: provide helpers for internal use Peter Xu
2017-09-22  9:04   ` Daniel P. Berrange
2017-09-22  9:14     ` Peter Xu
2017-09-22  9:36       ` Daniel P. Berrange
2017-09-22  9:38         ` Paolo Bonzini
2017-09-22  9:43           ` Daniel P. Berrange
2017-09-22 10:14             ` Paolo Bonzini
2017-09-22 10:17               ` Daniel P. Berrange
2017-09-22 12:59                 ` Fam Zheng
2017-09-22 13:03                   ` Paolo Bonzini
2017-09-22 10:54               ` Peter Xu
2017-09-22 10:16   ` Stefan Hajnoczi
2017-09-22 10:18     ` Paolo Bonzini
2017-09-22 10:20       ` Daniel P. Berrange
2017-09-22 10:26         ` Paolo Bonzini
2017-09-22 10:28           ` Daniel P. Berrange
2017-09-22 14:35             ` Stefan Hajnoczi
2017-09-22 14:55               ` Daniel P. Berrange
2017-10-02 17:18     ` Markus Armbruster
2017-10-08 12:46       ` Peter Xu
2017-09-22  8:56 ` [Qemu-devel] [PATCH 2/3] iothread: export iothread_stop() Peter Xu
2017-09-22 13:06   ` Fam Zheng
2017-09-25  3:29     ` Peter Xu
2017-09-22  8:56 ` Peter Xu [this message]
2017-09-22 13:09   ` [Qemu-devel] [PATCH 3/3] iothread: delay the context release to finalize Fam Zheng
2017-09-25  5:23     ` Peter Xu
2017-09-25  5:30       ` Fam Zheng
2017-09-25  5:50         ` Peter Xu
2017-09-25  5:58           ` Fam Zheng

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=1506070572-7549-4-git-send-email-peterx@redhat.com \
    --to=peterx@redhat.com \
    --cc=berrange@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=famz@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=shajnocz@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).