diff options
| author | Alexey Kardashevskiy <aik@ozlabs.ru> | 2020-03-25 16:25:42 +0100 |
|---|---|---|
| committer | David Gibson <david@gibson.dropbear.id.au> | 2020-05-07 11:10:50 +1000 |
| commit | 91067db1abcdc6caf951494b8d7e4bfaaa0cb61d (patch) | |
| tree | 468ad6624f9c0366f9158563ff83a4abb1092140 /dma-helpers.c | |
| parent | b4b83312e72461540ee155006f0d49e33bf0c58d (diff) | |
| download | qemu-91067db1abcdc6caf951494b8d7e4bfaaa0cb61d.zip qemu-91067db1abcdc6caf951494b8d7e4bfaaa0cb61d.tar.gz qemu-91067db1abcdc6caf951494b8d7e4bfaaa0cb61d.tar.bz2 | |
spapr/cas: Separate CAS handling from rebuilding the FDT
At the moment "ibm,client-architecture-support" ("CAS") is implemented
in SLOF and QEMU assists via the custom H_CAS hypercall which copies
an updated flatten device tree (FDT) blob to the SLOF memory which
it then uses to update its internal tree.
When we enable the OpenFirmware client interface in QEMU, we won't need
to copy the FDT to the guest as the client is expected to fetch
the device tree using the client interface.
This moves FDT rebuild out to a separate helper which is going to be
called from the "ibm,client-architecture-support" handler and leaves
writing FDT to the guest in the H_CAS handler.
This should not cause any behavioral change.
Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Message-Id: <20200310050733.29805-3-aik@ozlabs.ru>
Signed-off-by: Greg Kurz <groug@kaod.org>
Message-Id: <158514994229.478799.2178881312094922324.stgit@bahia.lan>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Diffstat (limited to 'dma-helpers.c')
0 files changed, 0 insertions, 0 deletions