From: Paolo Bonzini <pbonzini@redhat.com>
To: Bin Wu <wu.wubin@huawei.com>, Fam Zheng <famz@redhat.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] qemu-coroutine-lock: fix co_queue multi-adding bug
Date: Mon, 09 Feb 2015 10:37:02 +0100 [thread overview]
Message-ID: <54D87FBE.4070209@redhat.com> (raw)
In-Reply-To: <54D87F8A.7000509@huawei.com>
On 09/02/2015 10:36, Bin Wu wrote:
> During the mirror phase with nbd devices, if we send a cancel command or
> physical network breaks down, the source qemu process will receive a readable
> event and the main loop will invoke nbd_reply_ready to deal with it. This
> function finds the connection is down and then goes into
> nbd_teardown_connection. nbd_teardown_connection wakes up all working coroutines
> by nbd_recv_coroutines_enter_all. These coroutines include the one which holds
> the sending lock, the ones which wait for the lock, and the ones which wait for
> receiving messages.
>
> I think the purpose of nbd_recv_coroutines_enter_all is to terminate all waiting
> coroutines by waking all of them up. If the coroutine waiting for the lock is
> allowed for waking up, this implementation is ok. If not, we need to distinguish
> the coroutines waiting for receiving messages from the ones waiting for the lock.
>
> In my option, if the coroutines waiting for a lock is allowd for waking up, it
> should be more robust :>
No, it's not allowed.
Paolo
next prev parent reply other threads:[~2015-02-09 10:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-07 9:51 [Qemu-devel] [PATCH] fix the co_queue multi-adding bug w00214312
2015-02-07 9:51 ` [Qemu-devel] [PATCH] qemu-coroutine-lock: fix " w00214312
2015-02-09 8:12 ` Fam Zheng
2015-02-09 9:36 ` Bin Wu
2015-02-09 9:37 ` Paolo Bonzini [this message]
2015-02-09 10:12 ` Kevin Wolf
2015-02-10 1:08 ` Bin Wu
2015-02-09 9:23 ` [Qemu-devel] [PATCH] fix the " Paolo Bonzini
2015-02-09 9:47 ` Bin Wu
2015-02-10 6:34 ` Bin Wu
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=54D87FBE.4070209@redhat.com \
--to=pbonzini@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=wu.wubin@huawei.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).