From: Avi Kivity Subject: Re: [PATCH 0/2] eventfd: new EFD_STATE flag Date: Thu, 27 Aug 2009 07:13:32 +0300 Message-ID: <4A9607EC.2080304@redhat.com> References: <20090820182847.GB9282@redhat.com> <4A913DA9.1020403@redhat.com> <20090823133620.GA12841@redhat.com> <4A9146E3.2090007@redhat.com> <20090823143021.GA27495@redhat.com> <20090824214900.GA9899@redhat.com> <20090825072229.GA10608@redhat.com> <20090826102908.GA21523@redhat.com> <4A9585EC.2030505@redhat.com> <4A95900D.9090201@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Michael S. Tsirkin" , gleb@redhat.com, kvm@vger.kernel.org, Linux Kernel Mailing List To: Davide Libenzi Return-path: Received: from mx1.redhat.com ([209.132.183.28]:64728 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750755AbZH0ENG (ORCPT ); Thu, 27 Aug 2009 00:13:06 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 08/27/2009 02:30 AM, Davide Libenzi wrote: > On Wed, 26 Aug 2009, Davide Libenzi wrote: > > >>> I see no kernel equivalent to read(), but that's easily done. >>> >> Adding an in-kernel read based on "ctx", that is no problem at all. >> > Something like the untested below. > I had thought you said the eventfd readers where in userspace, but I might > have misunderstood you. > No, they're all over the place. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.