From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 05/24] compatfd is included before, and it is compiled unconditionally Date: Tue, 22 Sep 2009 09:34:38 -0400 Message-ID: <20090922133438.GA12443@infradead.org> References: <6e46fe952ba8d1896e3cab5b24232828d3f827a9.1253272938.git.quintela@redhat.com> <20090922131901.GA22109@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Christoph Hellwig , kvm@vger.kernel.org To: Juan Quintela Return-path: Received: from bombadil.infradead.org ([18.85.46.34]:59551 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754673AbZIVNef (ORCPT ); Tue, 22 Sep 2009 09:34:35 -0400 Content-Disposition: inline In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On Tue, Sep 22, 2009 at 03:25:13PM +0200, Juan Quintela wrote: > Christoph Hellwig wrote: > > Btw, what's the state of getting compatfd upstream? It's a pretty > > annoying difference between qemu upstream and qemu-kvm. > > I haven't tried. I can try to send a patch. Do you have any use case > that will help the cause? Well, the eventfd compat is used in the thread pool AIO code. I don't know what difference it makes, but I really hate this code beeing different in both trees. I want to see compatfd used either in both or none.