diff options
author | David Gibson <david@gibson.dropbear.id.au> | 2019-09-24 16:25:08 +1000 |
---|---|---|
committer | David Gibson <david@gibson.dropbear.id.au> | 2019-10-24 09:36:55 +1100 |
commit | 150e25f85baa7b7952ddd1bdfd7ff7801213ce51 (patch) | |
tree | 97ad4f22a4a76b93c422f3f508e623a399e87d79 /Makefile | |
parent | 29cb4187497dcc6be80c9cd2a87764be89d940f6 (diff) | |
download | qemu-150e25f85baa7b7952ddd1bdfd7ff7801213ce51.zip qemu-150e25f85baa7b7952ddd1bdfd7ff7801213ce51.tar.gz qemu-150e25f85baa7b7952ddd1bdfd7ff7801213ce51.tar.bz2 |
spapr, xics, xive: Introduce SpaprInterruptController QOM interface
The SpaprIrq structure is used to represent ths spapr machine's irq
backend. Except that it kind of conflates two concepts: one is the
backend proper - a specific interrupt controller that we might or
might not be using, the other is the irq configuration which covers
the layout of irq space and which interrupt controllers are allowed.
This leads to some pretty confusing code paths for the "dual"
configuration where its hooks redirect to other SpaprIrq structures
depending on the currently active irq controller.
To clean this up, we start by introducing a new
SpaprInterruptController QOM interface to represent strictly an
interrupt controller backend, not counting anything configuration
related. We implement this interface in the XICs and XIVE interrupt
controllers, and in future we'll move relevant methods from SpaprIrq
into it.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Greg Kurz <groug@kaod.org>
Reviewed-by: Cédric Le Goater <clg@kaod.org>
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions