From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Furukawa, Eiji" <e_furukawa@jp.fujitsu.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] main-loop.c: About Select handling
Date: Tue, 11 Dec 2012 11:12:10 +0100 [thread overview]
Message-ID: <20121211101210.GE796@stefanha-thinkpad.muc.redhat.com> (raw)
In-Reply-To: <9AFE08236B46DE418D958EE249411AC21B878E9C@g01jpexmbyt23>
On Thu, Dec 06, 2012 at 12:30:19AM +0000, Furukawa, Eiji wrote:
>
> The select() do not masked signal in os_host_main_loop_wait.
>
> For example, qemu-timer.c gives SIGALRM regularly.
> Even if a buffer of select is empty,
What does "a buffer of select is empty" mean?
> I think that it is a problem that this select() does exit by this SIGALRM.
The main loop will iterate again. Why is it a problem if select()
returns?
Stefan
next prev parent reply other threads:[~2012-12-11 10:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 3:08 [Qemu-devel] main-loop.c: About Select handling Furukawa, Eiji
2012-11-29 14:17 ` Stefan Hajnoczi
2012-12-06 0:30 ` Furukawa, Eiji
2012-12-11 10:12 ` Stefan Hajnoczi [this message]
2012-12-17 4:49 ` Furukawa, Eiji
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=20121211101210.GE796@stefanha-thinkpad.muc.redhat.com \
--to=stefanha@gmail.com \
--cc=e_furukawa@jp.fujitsu.com \
--cc=qemu-devel@nongnu.org \
/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).