From: Avi Kivity <avi@qumranet.com>
To: "Xu, Anthony" <anthony.xu@intel.com>
Cc: Jes Sorensen <jes@sgi.com>,
kvm-ia64@vger.kernel.org, "Zhang,
Xiantao" <xiantao.zhang@intel.com>,
kvm@vger.kernel.org
Subject: Re: [kvm-ia64-devel] IRQ assignment
Date: Wed, 21 May 2008 19:50:59 +0300 [thread overview]
Message-ID: <483452F3.2050404@qumranet.com> (raw)
In-Reply-To: <51CFAB8CB6883745AE7B93B3E084EBE201BCC44B@pdsmsx412.ccr.corp.intel.com>
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
next prev parent reply other threads:[~2008-05-21 16:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <yq0zlrkkbdn.fsf@jaguar.mkp.net>
[not found] ` <yq0ve28ka20.fsf@jaguar.mkp.net>
[not found] ` <yq0bq3yjnp6.fsf@jaguar.mkp.net>
[not found] ` <yq0k5hniuld.fsf@jaguar.mkp.net>
[not found] ` <51CFAB8CB6883745AE7B93B3E084EBE201BCC43D@pdsmsx412.ccr.corp.intel.com>
[not found] ` <4834459B.1090900@qumranet.com>
[not found] ` <51CFAB8CB6883745AE7B93B3E084EBE201BCC43E@pdsmsx412.ccr.corp.intel.com>
2008-05-21 16:16 ` [kvm-ia64-devel] IRQ assignment Avi Kivity
2008-05-21 16:47 ` Xu, Anthony
2008-05-21 16:50 ` Avi Kivity [this message]
2008-05-21 16:54 ` Xu, Anthony
[not found] ` <1284E411-576E-498A-A1D2-4B9F37E72533@suse.de>
2008-05-21 16:34 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=483452F3.2050404@qumranet.com \
--to=avi@qumranet.com \
--cc=anthony.xu@intel.com \
--cc=jes@sgi.com \
--cc=kvm-ia64@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=xiantao.zhang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox