Re: [PATCH RFC] x86/acpi: don't ignore I/O APICs just because there's no local APIC
From: Eric W. Biederman
Date: Thu Jun 18 2009 - 08:26:38 EST
Jeremy Fitzhardinge <jeremy@xxxxxxxx> writes:
> Actually I was discussing this with Keir yesterday. We're definitely open to
> changing the dom0 API to make things simpler on the Linux side. (The dom0 ABI
> is more fluid than the domU one, and these changes would be backwards-compatible
> One of the options we discussed was changing the API to get rid of the exposed
> vector, and just replace it with an operation to directly bind a gsi to a pirq
> (internal Xen physical interrupt handle, if you will), so that Xen ends up doing
> all the I/O APIC programming internally, as well as the local APIC.
> On the Linux side, I think it means we can just point pcibios_enable/disable_irq
> to our own xen_pci_irq_enable/disable functions to create the binding between a
> PCI device and an irq.
Then let's make this the plan. Design a supportable dom0 <-> kernel
irq abi. Essentially binding a gsi to an event channel mapping
function. Get that into Xen. Then get that into the mainstream linux
Regardless of the upstream linux kernel merge status cleaning up the
irq handling is going to have to happen to move past 2.6.18. I cleaned the
irq code up and changed it to work in incompatible ways starting in 2.6.19.
I really REALLY don't want to see support for Xen 3.4 domU irq
handling in the mainline linux kernel. It is an evolutionary dead
end, and I have already ripped that code out of linux once. Vectors
should be an implementation detail not an exposed part of the ABI.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/