From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [KVM-RFC PATCH 1/2] eventfd: add an explicit srcu based notifier interface Date: Thu, 18 Jun 2009 12:03:52 +0300 Message-ID: <4A3A02F8.6040301@redhat.com> References: <20090616022041.23890.90120.stgit@dev.haskins.net> <20090616022956.23890.63776.stgit@dev.haskins.net> <20090616140240.GA9401@redhat.com> <4A37AEF7.7070203@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Michael S. Tsirkin" , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, davidel@xmailserver.org, paulmck@linux.vnet.ibm.com To: Gregory Haskins Return-path: Received: from mx2.redhat.com ([66.187.237.31]:59744 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752615AbZFRJDc (ORCPT ); Thu, 18 Jun 2009 05:03:32 -0400 In-Reply-To: <4A37AEF7.7070203@novell.com> Sender: kvm-owner@vger.kernel.org List-ID: On 06/16/2009 05:40 PM, Gregory Haskins wrote: > > Something else to consider: For iosignalfd, we can assume we will > always be called from vcpu process context so we might not really need > official affirmation from the system. For irqfd, we cannot predict who > may be injecting the interrupt (for instance, it might be a > PCI-passthrough hard-irq context). I am not sure if this knowledge > actually helps to simplify the problem space, but I thought I should > mention it. > We can't assume anything. Userspace might hand out that eventfd to anyone. -- error compiling committee.c: too many arguments to function