From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 1/2] KVM: Distangle eventfd code from irqchip Date: Tue, 16 Oct 2012 12:57:18 +0200 Message-ID: <507D3D8E.1020903@redhat.com> References: <1350302566-28889-1-git-send-email-agraf@suse.de> <1350302566-28889-2-git-send-email-agraf@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: KVM list , kvm-ppc@vger.kernel.org To: Alexander Graf Return-path: Received: from mx1.redhat.com ([209.132.183.28]:10676 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753397Ab2JPK5Y (ORCPT ); Tue, 16 Oct 2012 06:57:24 -0400 In-Reply-To: <1350302566-28889-2-git-send-email-agraf@suse.de> Sender: kvm-owner@vger.kernel.org List-ID: On 10/15/2012 02:02 PM, Alexander Graf wrote: > The current eventfd code assumes that when we have eventfd, we also have > irqfd for in-kernel interrupt delivery. This is not necessarily true. On > PPC we don't have an in-kernel irqchip yet, but we can still support easily > support eventfd. > Don't you need, in addition, to reject PIO space for ioeventfd? -- error compiling committee.c: too many arguments to function