From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 4/4][RFC] kvm: eoi_eventfd Date: Sun, 24 Jun 2012 15:56:57 +0300 Message-ID: <4FE70E99.90609@redhat.com> References: <20120622220040.9858.43665.stgit@bling.home> <20120622221626.9858.33817.stgit@bling.home> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, jan.kiszka@siemens.com, mst@redhat.com To: Alex Williamson Return-path: Received: from mx1.redhat.com ([209.132.183.28]:52312 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754129Ab2FXM5D (ORCPT ); Sun, 24 Jun 2012 08:57:03 -0400 In-Reply-To: <20120622221626.9858.33817.stgit@bling.home> Sender: kvm-owner@vger.kernel.org List-ID: On 06/23/2012 01:16 AM, Alex Williamson wrote: > I think we're probably also going to need something like this. > When running in non-accelerated qemu, we're going to have to > create some kind of EOI notifier for drivers. VFIO can make > additional improvements when running on KVM so it will probably > make use of the KVM_IRQFD_LEVEL_EOI interface, but we don't > want to have a generic EOI notifier in qemu that just stops > working when kvm-ioapic is enabled. Why? -- error compiling committee.c: too many arguments to function