From: Laszlo Ersek <lersek@redhat.com>
To: Izumi Tsutsui <tsutsui@ceres.dti.ne.jp>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] semaphore: fix a hangup problem under loadon NetBSD hosts.
Date: Tue, 02 Jul 2013 17:47:27 +0200 [thread overview]
Message-ID: <51D2F60F.1020103@redhat.com> (raw)
In-Reply-To: <130703002742.M0121797@mirage.ceres.dti.ne.jp>
On 07/02/13 17:27, Izumi Tsutsui wrote:
> Laszlo Ersek wrote:
>> Conversely, the only time we need to send a signal is the 0->1 count
>> transition (*).
>
> Per comments from Soda, signals could be required even on count >0,
> if more than one threads are sleeping in qemu_cond_timedwait(),
> and more than one qemu_sem_post() are called at once, then
> the second qemu_sem_post() gets the mutex before sleeping threads
> in qemu_sem_timedwait().
You're right.
Laszlo
prev parent reply other threads:[~2013-07-02 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-29 10:22 [Qemu-devel] [PATCH] semaphore: fix a hangup problem under load on NetBSD hosts Izumi Tsutsui
2013-07-01 9:54 ` Laszlo Ersek
2013-07-02 15:27 ` [Qemu-devel] [PATCH] semaphore: fix a hangup problem under loadon " Izumi Tsutsui
2013-07-02 15:47 ` Laszlo Ersek [this message]
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=51D2F60F.1020103@redhat.com \
--to=lersek@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tsutsui@ceres.dti.ne.jp \
/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).