From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:57366) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QV2kV-0000x6-MI for qemu-devel@nongnu.org; Fri, 10 Jun 2011 10:31:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QV2kU-0001uT-1n for qemu-devel@nongnu.org; Fri, 10 Jun 2011 10:31:47 -0400 Received: from e2.ny.us.ibm.com ([32.97.182.142]:57372) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QV2kT-0001uL-Ol for qemu-devel@nongnu.org; Fri, 10 Jun 2011 10:31:45 -0400 Received: from d01relay06.pok.ibm.com (d01relay06.pok.ibm.com [9.56.227.116]) by e2.ny.us.ibm.com (8.14.4/8.13.1) with ESMTP id p5AEBMKU031820 for ; Fri, 10 Jun 2011 10:11:22 -0400 Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d01relay06.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p5AEVeer1085544 for ; Fri, 10 Jun 2011 10:31:40 -0400 Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p5A8VZbL029961 for ; Fri, 10 Jun 2011 02:31:36 -0600 Message-ID: <4DF22AC5.5060109@us.ibm.com> Date: Fri, 10 Jun 2011 09:31:33 -0500 From: Anthony Liguori MIME-Version: 1.0 References: <1307532813-27175-1-git-send-email-peter.maydell@linaro.org> <4DEF6B2B.7090305@siemens.com> <4DF0FCDA.5070804@siemens.com> <4DF21334.2070204@us.ibm.com> <4DF21F97.4070709@siemens.com> <4DF2264C.6080609@us.ibm.com> <4DF227D0.6000505@siemens.com> In-Reply-To: <4DF227D0.6000505@siemens.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH RFC 0/3] basic support for composing sysbus devices List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Peter Maydell , =?UTF-8?B?SnVoYSBSaWloaW3DpGtp?= , "patches@linaro.org" , "qemu-devel@nongnu.org" , Markus Armbruster , Paul Brook On 06/10/2011 09:18 AM, Jan Kiszka wrote: > On 2011-06-10 16:12, Anthony Liguori wrote: >> On 06/10/2011 08:43 AM, Jan Kiszka wrote: >> -device piix3,id=piix3 -device >> isa-serial,id=serial,irq[3]=piix3.irq[3],irq[4]=piix3.irq[4],... >> >> But I don't think we benefit from modelling it this correctly. The >> point is that the infrastructure could handle it though. > > I don't see the point of 'piix3.' in your IRQ assignment, though. It is > redundant to the bus assignment Bus assignment is the problem. IRQ routing cannot be tied strictly to buses if we want to be able to do composition. You could do clever things syntactically but the general mechanism is needed is the ability to wire things in an arbitrary fashion. Regards, Anthony Liguori - as the ISA bus also routes interrupts. > There are surely also buses that don't. Still, interrupt routing via the > bus should be possible (as it avoids boilerplate code or configuration > redundancy). > > Jan >