diff options
| author | David Gibson <david@gibson.dropbear.id.au> | 2019-10-02 11:53:57 +1000 |
|---|---|---|
| committer | David Gibson <david@gibson.dropbear.id.au> | 2019-11-26 10:11:30 +1100 |
| commit | b14848f5d757cbe89dfd1ee68ce701a8277c2f17 (patch) | |
| tree | f9ae8876968f2843aaf9fb95be50bb67417fd5e0 /tests/test-string-input-visitor.c | |
| parent | e532e1d93c4bd869b11db6ee0de2057e7d288889 (diff) | |
| download | qemu-b14848f5d757cbe89dfd1ee68ce701a8277c2f17.zip qemu-b14848f5d757cbe89dfd1ee68ce701a8277c2f17.tar.gz qemu-b14848f5d757cbe89dfd1ee68ce701a8277c2f17.tar.bz2 | |
spapr: Work around spurious warnings from vfio INTx initialization
Traditional PCI INTx for vfio devices can only perform well if using
an in-kernel irqchip. Therefore, vfio_intx_update() issues a warning
if an in kernel irqchip is not available.
We usually do have an in-kernel irqchip available for pseries machines
on POWER hosts. However, because the platform allows feature
negotiation of what interrupt controller model to use, we don't
currently initialize it until machine reset. vfio_intx_update() is
called (first) from vfio_realize() before that, so it can issue a
spurious warning, even if we will have an in kernel irqchip by the
time we need it.
To workaround this, make a call to spapr_irq_update_active_intc() from
spapr_irq_init() which is called at machine realize time, before the
vfio realize. This call will be pretty much obsoleted by the later
call at reset time, but it serves to suppress the spurious warning
from VFIO.
Cc: Alex Williamson <alex.williamson@redhat.com>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Cédric Le Goater <clg@kaod.org>
Tested-by: Alex Williamson <alex.williamson@redhat.com>
Reviewed-by: Alex Williamson <alex.williamson@redhat.com>
Reviewed-by: Greg Kurz <groug@kaod.org>
Acked-by: Alex Williamson <alex.williamson@redhat.com>
Diffstat (limited to 'tests/test-string-input-visitor.c')
0 files changed, 0 insertions, 0 deletions