On Wed, Jul 18, 2018 at 8:28 AM, Alistair Francis <alistair.fran...@wdc.com> wrote:
> Use the new object_initialize_child() and sysbus_init_child_obj() to > fix the issue. > > Signed-off-by: Alistair Francis <alistair.fran...@wdc.com> > Reviewed-by: Michael Clark <m...@sifive.com> > --- > hw/riscv/virt.c | 5 ++--- > 1 file changed, 2 insertions(+), 3 deletions(-) > > diff --git a/hw/riscv/virt.c b/hw/riscv/virt.c > index aeada2498d..248bbdffd3 100644 > --- a/hw/riscv/virt.c > +++ b/hw/riscv/virt.c > @@ -274,9 +274,8 @@ static void riscv_virt_board_init(MachineState > *machine) > void *fdt; > > /* Initialize SOC */ > - object_initialize(&s->soc, sizeof(s->soc), TYPE_RISCV_HART_ARRAY); > - object_property_add_child(OBJECT(machine), "soc", OBJECT(&s->soc), > - &error_abort); > + object_initialize_child(OBJECT(machine), "soc", &s->soc, > sizeof(s->soc), > + TYPE_RISCV_HART_ARRAY, &error_abort, NULL); > object_property_set_str(OBJECT(&s->soc), VIRT_CPU, "cpu-type", > &error_abort); > object_property_set_int(OBJECT(&s->soc), smp_cpus, "num-harts", > -- > 2.17.1 > >
