Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754570Ab0AURON (ORCPT ); Thu, 21 Jan 2010 12:14:13 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752948Ab0AUROL (ORCPT ); Thu, 21 Jan 2010 12:14:11 -0500 Received: from mx1.redhat.com ([209.132.183.28]:53637 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752726Ab0AUROJ (ORCPT ); Thu, 21 Jan 2010 12:14:09 -0500 Message-ID: <4B588B5D.8050802@redhat.com> Date: Thu, 21 Jan 2010 19:14:05 +0200 From: Avi Kivity User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5) Gecko/20091209 Fedora/3.0-4.fc12 Thunderbird/3.0 MIME-Version: 1.0 To: Davide Libenzi CC: "Michael S. Tsirkin" , mtosatti@redhat.com, kvm@vger.kernel.org, Linux Kernel Mailing List Subject: Re: [PATCHv2 1/3] eventfd: allow atomic read and waitqueue remove References: <20100121162648.GA16458@redhat.com> <4B588B29.2050100@redhat.com> In-Reply-To: <4B588B29.2050100@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 661 Lines: 18 On 01/21/2010 07:13 PM, Avi Kivity wrote: > > But I think we can solve this in another way in .32: we can clear the > eventfd from irqfd->inject work, which is in process context. The new > stuff is only needed for lockless clearing, no? > I meant atomic clearing, when we inject interrupts from the irqfd atomic context. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/