From: Gerd Hoffmann <kraxel@redhat.com>
To: Yonit Halperin <yhalperi@redhat.com>,
qemu-devel@nongnu.org, spice-devel@freedesktop.org
Subject: Re: [Qemu-devel] [Spice-devel] [PATCH] server: don't call reds_stream_free from worker thread context
Date: Mon, 05 Sep 2011 15:29:39 +0200 [thread overview]
Message-ID: <4E64CEC3.3030108@redhat.com> (raw)
In-Reply-To: <20110905104700.GN27006@bow>
Hi,
> I verified it still calls reds_stream_free from the worker thread, only
> now the call itself is done in red_channel.c (via red_channel_disconnect
> or something like that), which is called from red_worker.c
Where the code in red_channel.c is now shared for all channel types?
Hmm. That makes it a bit harder to change the workflow I guess ...
cheers,
Gerd
next prev parent reply other threads:[~2011-09-05 13:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 15:19 [Qemu-devel] [PATCH] server: don't call reds_stream_free from worker thread context Gerd Hoffmann
2011-09-02 19:27 ` [Qemu-devel] [Spice-devel] " Alon Levy
2011-09-04 8:43 ` Yonit Halperin
2011-09-05 9:02 ` Gerd Hoffmann
2011-09-05 10:47 ` Alon Levy
2011-09-05 13:29 ` Gerd Hoffmann [this message]
2011-09-05 13:44 ` Alon Levy
2011-09-05 13:45 ` Alon Levy
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=4E64CEC3.3030108@redhat.com \
--to=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=spice-devel@freedesktop.org \
--cc=yhalperi@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).