From: Avi Kivity Subject: Re: [PATCH 0/2] eventfd: new EFD_STATE flag Date: Sun, 23 Aug 2009 16:40:51 +0300 Message-ID: <4A9146E3.2090007@redhat.com> References: <20090820155655.GA8764@redhat.com> <4A8D8A28.2050004@redhat.com> <20090820175540.GA9232@redhat.com> <4A8D90BB.2030506@redhat.com> <20090820182847.GB9282@redhat.com> <4A913DA9.1020403@redhat.com> <20090823133620.GA12841@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Davide Libenzi , gleb@redhat.com, kvm@vger.kernel.org, Linux Kernel Mailing List To: "Michael S. Tsirkin" Return-path: Received: from mx1.redhat.com ([209.132.183.28]:45957 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933753AbZHWNkv (ORCPT ); Sun, 23 Aug 2009 09:40:51 -0400 In-Reply-To: <20090823133620.GA12841@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 08/23/2009 04:36 PM, Michael S. Tsirkin wrote: > More important here is realization that eventfd is a mutex/semaphore > implementation, not a generic event reporting interface as we are trying > to use it. > Well it is a generic event reporting interface (for example, aio uses it). -- error compiling committee.c: too many arguments to function