aboutsummaryrefslogtreecommitdiff
path: root/hw/i386
diff options
context:
space:
mode:
authorDavid Gibson <david@gibson.dropbear.id.au>2017-06-06 17:05:53 +1000
committerDavid Gibson <david@gibson.dropbear.id.au>2017-06-08 14:38:26 +1000
commit7b7258f810d2bd40e2fb99c469c5db318d6c3d92 (patch)
tree229e5bb5c345c0d62b2a0b0a44a19a8e338d0ebc /hw/i386
parent454b580ae9ae3e7722f1cd5f6da7bb479f86bbd8 (diff)
downloadqemu-7b7258f810d2bd40e2fb99c469c5db318d6c3d92.zip
qemu-7b7258f810d2bd40e2fb99c469c5db318d6c3d92.tar.gz
qemu-7b7258f810d2bd40e2fb99c469c5db318d6c3d92.tar.bz2
spapr: Clean up RTAS set-indicator
In theory the RTAS set-indicator call can be used for a number of "indicators" defined by PAPR. In practice the only ones we're ever likely to implement are those used for Dynamic Reconfiguration (i.e. hotplug). Because of this, the current implementation determines the associated DRC object, before dispatching based on the type of indicator. However, this means we also need a check that we're dealing with a DR related indicator at all, which duplicates some of the logic from the switch further down. Even though it means a bit of code duplication, things work out cleaner if we delegate the DRC lookup to the individual indicator type functions - and it also allows some further cleanups. While we're there, remove references to "sensor", a copy/paste artefact from the related, but distinct "get-sensor" call. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Reviewed-by: Michael Roth <mdroth@linux.vnet.ibm.com> Acked-by: Michael Roth <mdroth@linux.vnet.ibm.com>
Diffstat (limited to 'hw/i386')
0 files changed, 0 insertions, 0 deletions