spapr: Use less cryptic representation of which irq backends are supported
commitca62823b79443e3f498c6e6b9fea5f8bbe61033e
authorDavid Gibson <david@gibson.dropbear.id.au>
Wed, 25 Sep 2019 05:12:07 +0000 (25 15:12 +1000)
committerDavid Gibson <david@gibson.dropbear.id.au>
Fri, 4 Oct 2019 09:08:23 +0000 (4 19:08 +1000)
tree1b2e838e044ab583a81d8b998d14feedef313a8b
parente594c2ad1c3207ff308449203fd5abc002ac89c9
spapr: Use less cryptic representation of which irq backends are supported

SpaprIrq::ov5 stores the value for a particular byte in PAPR option vector
5 which indicates whether XICS, XIVE or both interrupt controllers are
available.  As usual for PAPR, the encoding is kind of overly complicated
and confusing (though to be fair there are some backwards compat things it
has to handle).

But to make our internal code clearer, have SpaprIrq encode more directly
which backends are available as two booleans, and derive the OV5 value from
that at the point we need it.

Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Cédric Le Goater <clg@kaod.org>
Reviewed-by: Greg Kurz <groug@kaod.org>
hw/ppc/spapr.c
hw/ppc/spapr_hcall.c
hw/ppc/spapr_irq.c
include/hw/ppc/spapr_irq.h