Re: [kvm-ia64-devel] IRQ assignment

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

--
To unsubscribe from this list: send the line "unsubscribe kvm-ia64" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux KVM Devel]     [Linux Virtualization]     [Big List of Linux Books]     [Linux SCSI]     [Yosemite Forum]

  Powered by Linux