While working on cpu hotplug for mach-virt, I've noticed that DTB
is generated incrementally across whole machvirt_init(). While it's
fine for machines with static DTB, it won't really work in case of
cpu hotplug and followed up reset since machine will load old DTB
that doesn't account for hotplugged CPUs.
So I've set on a quest to consolidate DTB generation and make it
reentrant so that on reset guest would see update DTB.
It's preliminary series which makes possible to call load_dtb()
later outside of arm_load_kernel() and in process of it drops
several machine_done notifiers, that were introduced to make
plaform-bus-devices work. Hopefully it makes code easier to follow.
It replaces machine_done notifiers with device hotplug framework
to allow for dynamic sysbus devices mapping at the moment they
are created instead of waiting for machine_done time and trying to
juggle with notifiers order to do initialization in propper order.
Mostly 'make check' tested +
manually with "ppce500" machine type and eTSEC device
(eTSEC is still initialized with the same IRQs as before series)
CC: qemu-arm@nongnu.org
CC: peter.maydell@linaro.org
CC: eric.auger@redhat.com
Igor Mammedov (4):
arm: reuse arm_boot_address_space() in armv7m_load_kernel()
platform-bus-device: use device plug callback instead of machine_done
notifier
arm: always start from first_cpu when registering loader cpu reset
callback
arm/boot: split load_dtb() from arm_load_kernel()
hw/ppc/e500.h | 3 ++
include/hw/arm/arm.h | 39 ++++++++++++-----
include/hw/arm/sysbus-fdt.h | 37 ++++------------
include/hw/arm/virt.h | 3 ++
include/hw/platform-bus.h | 4 +-
hw/arm/armv7m.c | 10 +----
hw/arm/boot.c | 85 +++++++++++--------------------------
hw/arm/sysbus-fdt.c | 67 +++--------------------------
hw/arm/virt.c | 100 +++++++++++++++++++++++++++++---------------
hw/core/platform-bus.c | 29 +++----------
hw/ppc/e500.c | 37 +++++++++-------
hw/ppc/e500plat.c | 60 +++++++++++++++++++++++++-
12 files changed, 227 insertions(+), 247 deletions(-)
--
2.7.4