From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:39947) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RXC2I-0007OO-D4 for qemu-devel@nongnu.org; Sun, 04 Dec 2011 08:23:19 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RXC2H-0005Wy-CP for qemu-devel@nongnu.org; Sun, 04 Dec 2011 08:23:18 -0500 Received: from mx1.redhat.com ([209.132.183.28]:33873) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RXC2H-0005Wu-15 for qemu-devel@nongnu.org; Sun, 04 Dec 2011 08:23:17 -0500 Message-ID: <4EDB7440.2010308@redhat.com> Date: Sun, 04 Dec 2011 15:23:12 +0200 From: Avi Kivity MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC][PATCH 11/16] kvm: Introduce core services for in-kernel irqchip support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Anthony Liguori , kvm@vger.kernel.org, "Michael S. Tsirkin" , Marcelo Tosatti , qemu-devel , Blue Swirl On 12/03/2011 01:17 PM, Jan Kiszka wrote: > From: Jan Kiszka > > Add the basic infrastructure to active in-kernel irqchip support, inject > interrupts into these models, and maintain IRQ routes. > > Routing is optional and depends on the host arch supporting > KVM_CAP_IRQ_ROUTING. When it's not available on x86, we loose the HPET lose > as we can't route GSI0 to IOAPIC pin 2. > > In-kernel irqchip support will once be controlled by the machine > property 'kernel_irqchip', but this is not yet wired up. > > -- error compiling committee.c: too many arguments to function