diff options
author | Greg Kurz <groug@kaod.org> | 2017-07-24 14:34:33 +0200 |
---|---|---|
committer | Alexey Kardashevskiy <aik@ozlabs.ru> | 2017-07-25 15:10:03 +1000 |
commit | 604d28cc3f791657414f8b21103921fa0147fc63 (patch) | |
tree | b441d3c6e41f8d1659782a4f4fb3c80f1101e67d /lib/libvirtio/virtio-net.c | |
parent | 89f519f09bf850918b60526e50409afb663418aa (diff) | |
download | SLOF-604d28cc3f791657414f8b21103921fa0147fc63.zip SLOF-604d28cc3f791657414f8b21103921fa0147fc63.tar.gz SLOF-604d28cc3f791657414f8b21103921fa0147fc63.tar.bz2 |
board-qemu: add private hcall to inform host on "phandle" update
The "interrupt-map" property in each PHB node references the "phandle"
property of the "interrupt-controller" node. This is used by the guest
OS to setup IRQs for any PCI device plugged into the PHB. QEMU sets this
property to an arbitrary value in the flattened DT passed to SLOF.
Since commit 82954d4c1088, SLOF has some generic code to convert all
references to any "phandle" property to a SLOF specific value.
This is is perfectly okay for coldplug devices, since the guest OS only
sees the converted value in "interrupt-map". It is a problem though for
hotplug devices. Since they don't go through SLOF, the guest OS receives
the arbitrary value set by QEMU and fails to setup IRQs.
In order to support PHB hotplug, this patch introduces a new private
hcall, which allows SLOF to tell QEMU that a "phandle" was converted
from an old value to a new value.
Suggested-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Greg Kurz <groug@kaod.org>
Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Diffstat (limited to 'lib/libvirtio/virtio-net.c')
0 files changed, 0 insertions, 0 deletions