2aff696b10
The guest is permitted to specify an arbitrary domain/bus/device/function and INTX pin from which the callback IRQ shall appear to have come. In QEMU we can only easily do this for devices that actually exist, and even that requires us "knowing" that it's a PCMachine in order to find the PCI root bus — although that's OK really because it's always true. We also don't get to get notified of INTX routing changes, because we can't do that as a passive observer; if we try to register a notifier it will overwrite any existing notifier callback on the device. But in practice, guests using PCI_INTX will only ever use pin A on the Xen platform device, and won't swizzle the INTX routing after they set it up. So this is just fine. Signed-off-by: David Woodhouse <dwmw@amazon.co.uk> Reviewed-by: Paul Durrant <paul@xen.org> |
||
|---|---|---|
| .. | ||
| apic.c | ||
| clock.c | ||
| i8254.c | ||
| i8259.c | ||
| ioapic.c | ||
| meson.build | ||
| xen_evtchn.c | ||
| xen_evtchn.h | ||
| xen_overlay.c | ||
| xen_overlay.h | ||
| xen-stubs.c | ||