From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH v8 18/18] kvm: Activate in-kernel irqchip support Date: Tue, 24 Jan 2012 16:05:35 +0200 Message-ID: <4F1EBAAF.8040808@redhat.com> References: <6a48ffaaa732b2142c1b5030178f2d4a0fa499fe.1326972302.git.jan.kiszka@siemens.com> <20120119180851.GA19099@amt.cnet> <4F1866E0.7010900@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Marcelo Tosatti , Anthony Liguori , kvm@vger.kernel.org, "Michael S. Tsirkin" , qemu-devel , Blue Swirl To: Jan Kiszka Return-path: Received: from mx1.redhat.com ([209.132.183.28]:58733 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751809Ab2AXOFn (ORCPT ); Tue, 24 Jan 2012 09:05:43 -0500 In-Reply-To: <4F1866E0.7010900@web.de> Sender: kvm-owner@vger.kernel.org List-ID: On 01/19/2012 08:54 PM, Jan Kiszka wrote: > Nope, see kvm_irqchip_create, patch 13. You can also check by browsing > the qtree (different device model names). That was my biggest objection to the previous iterations. Later versions changed to use an attribute (selecting the backend). What happened now? -- error compiling committee.c: too many arguments to function