From: Liu Yuan <namei.unix@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] 100% CPU when sockfd is half-closed and unexpected behavior for qemu_co_send()
Date: Wed, 16 Jan 2013 14:39:24 +0800 [thread overview]
Message-ID: <50F64B1C.6050504@gmail.com> (raw)
In-Reply-To: <50F3D8F7.5010400@redhat.com>
On 01/14/2013 06:07 PM, Paolo Bonzini wrote:
> Ok. I guess the problem is that we use select(), not poll(), so we have
> no way to get POLLHUP notifications. But the write fd_set receives the
> file descriptor because indeed writes will not block.
Hi Paolo,
is there any movement switch select() to poll()?
Thanks,
Yuan
next prev parent reply other threads:[~2013-01-16 6:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 8:16 [Qemu-devel] 100% CPU when sockfd is half-closed and unexpected behavior for qemu_co_send() Liu Yuan
2013-01-14 9:09 ` Paolo Bonzini
2013-01-14 9:29 ` Liu Yuan
2013-01-14 10:07 ` Paolo Bonzini
2013-01-16 6:39 ` Liu Yuan [this message]
2013-01-14 10:23 ` Stefan Hajnoczi
2013-01-14 10:26 ` Liu Yuan
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=50F64B1C.6050504@gmail.com \
--to=namei.unix@gmail.com \
--cc=aliguori@us.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).