aboutsummaryrefslogtreecommitdiff
path: root/scripts/analyze-migration.py
diff options
context:
space:
mode:
authorDavid Gibson <david@gibson.dropbear.id.au>2019-11-29 15:00:58 +1100
committerDavid Gibson <david@gibson.dropbear.id.au>2019-12-17 10:39:48 +1100
commit0c21e073541cc093b4cb8744640e24f130e6f8ba (patch)
treef225c773a9899ed22a9f2828d4db953e6cab63f7 /scripts/analyze-migration.py
parent97b32a6afa78ae68fb16344b9a144b6f433f42a2 (diff)
downloadqemu-0c21e073541cc093b4cb8744640e24f130e6f8ba.zip
qemu-0c21e073541cc093b4cb8744640e24f130e6f8ba.tar.gz
qemu-0c21e073541cc093b4cb8744640e24f130e6f8ba.tar.bz2
spapr: Fold h_cas_compose_response() into h_client_architecture_support()
spapr_h_cas_compose_response() handles the last piece of the PAPR feature negotiation process invoked via the ibm,client-architecture-support OF call. Its only caller is h_client_architecture_support() which handles most of the rest of that process. I believe it was placed in a separate file originally to handle some fiddly dependencies between functions, but mostly it's just confusing to have the CAS process split into two pieces like this. Now that compose response is simplified (by just generating the whole device tree anew), it's cleaner to just fold it into h_client_architecture_support(). Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Reviewed-by: Cedric Le Goater <clg@fr.ibm.com> Reviewed-by: Greg Kurz <groug@kaod.org>
Diffstat (limited to 'scripts/analyze-migration.py')
0 files changed, 0 insertions, 0 deletions