From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [kvm-ia64-devel] IRQ assignment Date: Wed, 21 May 2008 19:50:59 +0300 Message-ID: <483452F3.2050404@qumranet.com> References: <51CFAB8CB6883745AE7B93B3E084EBE201BCC43D@pdsmsx412.ccr.corp.intel.com> <4834459B.1090900@qumranet.com> <51CFAB8CB6883745AE7B93B3E084EBE201BCC43E@pdsmsx412.ccr.corp.intel.com> <48344ACD.6030702@qumranet.com> <51CFAB8CB6883745AE7B93B3E084EBE201BCC44B@pdsmsx412.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jes Sorensen , kvm-ia64@vger.kernel.org, "Zhang, Xiantao" , kvm@vger.kernel.org To: "Xu, Anthony" Return-path: Received: from bzq-179-150-194.static.bezeqint.net ([212.179.150.194]:54360 "EHLO il.qumranet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752055AbYEUQvB (ORCPT ); Wed, 21 May 2008 12:51:01 -0400 In-Reply-To: <51CFAB8CB6883745AE7B93B3E084EBE201BCC44B@pdsmsx412.ccr.corp.intel.com> Sender: kvm-owner@vger.kernel.org List-ID: Xu, Anthony wrote: >> >> You can use this method for ia64, and we'll have a different function >> for x86 (perhaps two functions, if we later increase the number of >> pins to 48 (or even more); the DSDT will need to select the >> appropriate routing table according to what's present on the >> hardware). >> > It can work if X86 and ia64 implement different "->map" function. > > Use this kind of "fixed" algorithm may waste IOAPIC interrupt pin, due > to not every pci device will use up 4 irq. > > Is it possible to let qemu dynamically build route table in DSDT? > x86 and ia64 have different DSDTs, so I don't see the need for dynamic generation. The x86 DSDT can return different routing tables depending on whether one or two ioapics are present (this can be detected at runtime). -- error compiling committee.c: too many arguments to function