public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
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/6] Add support for eventfd() (v3)
Date: Thu, 08 May 2008 20:16:16 +0300	[thread overview]
Message-ID: <48233560.30308@qumranet.com> (raw)
In-Reply-To: <1210179349-27422-1-git-send-email-aliguori@us.ibm.com>

Anthony Liguori wrote:
> This patch adds compatibility code so that we can make use of eventfd() within
> QEMU.  eventfd() is a pretty useful mechanism as it allows multiple
> notifications to be batched in a single system call.
>
> We emulate eventfd() using a standard pipe().
>   

Applied all six patches; thanks.

-- 

Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
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

      parent reply	other threads:[~2008-05-08 17:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-07 16:55 [PATCH 1/6] Add support for eventfd() (v3) Anthony Liguori
2008-05-07 16:55 ` [PATCH 2/6] Replace SIGUSR1 in io-thread with " Anthony Liguori
2008-05-07 16:55 ` [PATCH 3/6] Add support for signalfd() (v3) Anthony Liguori
2008-05-07 16:55 ` [PATCH 4/6] Use signalfd() in io-thread (v3) Anthony Liguori
2008-05-07 16:55 ` [PATCH 5/6] Interrupt io thread in qemu_set_fd_handler2 (v3) Anthony Liguori
2008-05-07 16:55 ` [PATCH 6/6] Only select once per-main_loop iteration (v3) Anthony Liguori
2008-05-08 17:16 ` Avi Kivity [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=48233560.30308@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox