From: Avi Kivity <avi@qumranet.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: kvm-devel@lists.sourceforge.net, Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH 1/3] Use signalfd() in io-thread
Date: Mon, 05 May 2008 10:23:22 +0300 [thread overview]
Message-ID: <481EB5EA.9060605@qumranet.com> (raw)
In-Reply-To: <1209932438-6957-1-git-send-email-aliguori@us.ibm.com>
Anthony Liguori wrote:
> This patch reworks the IO thread to use signalfd() instead of sigtimedwait().
> This will eliminate the need to use SIGIO everywhere. In this version of the
> patch, we use signalfd() when it's available. When it isn't available, we
> create a separate thread and use sigwaitinfo() to simulate signalfd().
>
> We cannot handle thread-specific signals with signalfd() emulation so also
> replace SIGUSR1 notifications to the io-thread with an eventfd. Since eventfd
> isn't always available, use pipe() to emulate eventfd.
>
Please break the SIGUSR1 changes into a separate patch. Ditto with *fd
syscall compat.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
next prev parent reply other threads:[~2008-05-05 7:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-04 20:20 [PATCH 1/3] Use signalfd() in io-thread Anthony Liguori
2008-05-04 20:20 ` [PATCH 2/3] Interrupt io thread in qemu_set_fd_handler2 Anthony Liguori
2008-05-04 20:20 ` [PATCH 3/3] Only select once per-main_loop iteration Anthony Liguori
2008-05-05 7:23 ` Avi Kivity [this message]
[not found] ` <481F121A.9020207@us.ibm.com>
2008-05-05 14:27 ` [PATCH 1/3] Use signalfd() in io-thread Avi Kivity
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=481EB5EA.9060605@qumranet.com \
--to=avi@qumranet.com \
--cc=aliguori@us.ibm.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=mtosatti@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.