]> www.infradead.org Git - users/dwmw2/qemu.git/commit
hw/xen: Support HVM_PARAM_CALLBACK_TYPE_PCI_INTX callback xenfv-kvm-3
authorDavid Woodhouse <dwmw@amazon.co.uk>
Fri, 16 Dec 2022 00:03:21 +0000 (00:03 +0000)
committerDavid Woodhouse <dwmw@amazon.co.uk>
Fri, 16 Dec 2022 00:03:34 +0000 (00:03 +0000)
commit8efab62d7ff23b752690a33e57165d057855c0b2
tree0c4f2085835af7f0dd704be5c16c6ae0eda2dbbe
parent15a91ff4833d07910abba1dec093e48580c2b4c4
hw/xen: Support HVM_PARAM_CALLBACK_TYPE_PCI_INTX callback

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>
hw/i386/kvm/xen_evtchn.c