From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [PATCH v8 18/18] kvm: Activate in-kernel irqchip support Date: Tue, 24 Jan 2012 15:10:31 +0100 Message-ID: <4F1EBBD7.2050007@siemens.com> References: <6a48ffaaa732b2142c1b5030178f2d4a0fa499fe.1326972302.git.jan.kiszka@siemens.com> <20120119180851.GA19099@amt.cnet> <4F1866E0.7010900@web.de> <4F1EBAAF.8040808@redhat.com> 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: Avi Kivity Return-path: Received: from thoth.sbs.de ([192.35.17.2]:32713 "EHLO thoth.sbs.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755055Ab2AXOKo (ORCPT ); Tue, 24 Jan 2012 09:10:44 -0500 In-Reply-To: <4F1EBAAF.8040808@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 2012-01-24 15:05, Avi Kivity wrote: > 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? The other approach was rejected. Moreover, see http://thread.gmane.org/gmane.comp.emulators.qemu/129659, QOM will allow addressing with identical paths. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:50571) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rph55-00037u-JV for qemu-devel@nongnu.org; Tue, 24 Jan 2012 09:10:45 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Rph53-0002Vj-T3 for qemu-devel@nongnu.org; Tue, 24 Jan 2012 09:10:39 -0500 Received: from thoth.sbs.de ([192.35.17.2]:30324) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rph53-0002VP-De for qemu-devel@nongnu.org; Tue, 24 Jan 2012 09:10:37 -0500 Message-ID: <4F1EBBD7.2050007@siemens.com> Date: Tue, 24 Jan 2012 15:10:31 +0100 From: Jan Kiszka MIME-Version: 1.0 References: <6a48ffaaa732b2142c1b5030178f2d4a0fa499fe.1326972302.git.jan.kiszka@siemens.com> <20120119180851.GA19099@amt.cnet> <4F1866E0.7010900@web.de> <4F1EBAAF.8040808@redhat.com> In-Reply-To: <4F1EBAAF.8040808@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v8 18/18] kvm: Activate in-kernel irqchip support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Anthony Liguori , kvm@vger.kernel.org, "Michael S. Tsirkin" , Marcelo Tosatti , qemu-devel , Blue Swirl On 2012-01-24 15:05, Avi Kivity wrote: > 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? The other approach was rejected. Moreover, see http://thread.gmane.org/gmane.comp.emulators.qemu/129659, QOM will allow addressing with identical paths. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux