Jes Sorensen wrote:
>>>>>> "Jes" == Jes Sorensen <jes@xxxxxxx> writes:
>
> Jes> I think we have a general irq assignment problem. I just tried
> Jes> modprobing the sym53c8xx driver and I get the same issue that it
> Jes> cannot obtain an interrupt.
>
> Hi
>
> With commit c1f47ba4a598c47636c894c4feb81fe4c0b6ecd5 I now see
> interrupts being assigned to the various devices, however I still see
> no interrupts being delivered when I try to configure networking. Zero
> interrupts delivered in /proc/interrupts, however I see outgoing
> packets being delivers. I tried multiple network devices (e1000,
> rtl8139, ne2000), all show the same problem.
>
> Did anyone manage to get networking working under KVM/ia64?
Hi Jes/Avi,
Xiantao and I have found the root cause,
Qemu emulates PIIX chipset, all pci devices can only use irq 10.11,
which is confiured inside chipset interrupt routing table. Even though
IOAPIC have 24 interrupt pins.
While KVM/IA64 use the same Guest Firmware with what XEN/IA64 which use
different "interrupt routing algorithm".
Means the pci device irq doesn't match between qemu and Guest Firmware
in KVM/IA64. So guest didn't get pci device interrupt.
Obviously there are two ways to fix it.
1. modify qemu side, all pci devices use irq larger than or equal to 16,
we need to come out an algorithm to calculate irq from pci device(bus
number,device number, function number),
then we also need to modify IA32 Guest BIOS to present the same pci
device irq (use same algorithm) to guest OS. Avi seems not want to
modify qemu a lot.
2. modify IA64 guest firmware, two pros, (1)all pci devices use only
10,11 two irqs, so if there are many pci device, there are a lot of
interrupt sharing, which impact performance negatively
(2) We need to maintain two versions fo IA64 guest firmwares, one
for KVM/IA64, the other for XEN/IA64, which is not what I want.
What's your suggestion?
Thanks,
Anthony
--
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
