[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v1 3/5] xlnx-zcu102: Specify the valid CPUs
From: |
Igor Mammedov |
Subject: |
Re: [Qemu-devel] [PATCH v1 3/5] xlnx-zcu102: Specify the valid CPUs |
Date: |
Wed, 4 Oct 2017 13:12:32 +0200 |
On Tue, 3 Oct 2017 14:41:17 -0700
Alistair Francis <address@hidden> wrote:
> On Tue, Oct 3, 2017 at 1:36 PM, Eduardo Habkost <address@hidden> wrote:
> > On Tue, Oct 03, 2017 at 01:05:13PM -0700, Alistair Francis wrote:
> >> List all possible valid CPU options.
> >>
> >> Signed-off-by: Alistair Francis <address@hidden>
> >> ---
> >>
> >> hw/arm/xlnx-zcu102.c | 10 ++++++++++
> >> hw/arm/xlnx-zynqmp.c | 16 +++++++++-------
> >> include/hw/arm/xlnx-zynqmp.h | 1 +
> >> 3 files changed, 20 insertions(+), 7 deletions(-)
> >>
> >> diff --git a/hw/arm/xlnx-zcu102.c b/hw/arm/xlnx-zcu102.c
> >> index 519a16ed98..039649e522 100644
> >> --- a/hw/arm/xlnx-zcu102.c
> >> +++ b/hw/arm/xlnx-zcu102.c
> >> @@ -98,6 +98,8 @@ static void xlnx_zynqmp_init(XlnxZCU102 *s, MachineState
> >> *machine)
> >> object_property_add_child(OBJECT(machine), "soc", OBJECT(&s->soc),
> >> &error_abort);
> >>
> >> + object_property_set_str(OBJECT(&s->soc), machine->cpu_type,
> >> "cpu-type",
> >> + &error_fatal);
> >
> > Do you have plans to support other CPU types to xlnx_zynqmp in
> > the future? If not, I wouldn't bother adding the cpu-type
> > property and the extra boilerplate code if it's always going to
> > be set to cortex-a53.
>
> No, it'll always be A53.
>
> I did think of that, but I also wanted to use the new option! I also
> think there is an advantage in sanely handling users '-cpu' option,
> before now we just ignored it, so I think it still does give a
> benefit. That'll be especially important on the Xilinx tree (sometimes
> people use our machines with a different CPU to 'benchmark' or test
> other CPUs with our CoSimulation setup). So I think it does make sense
> to keep in.
if cpu isn't user settable, one could just outright die if cpu_type
is not NULL and say that user's CLI is wrong.
(i.e. don't give users illusion that they allowed to use '-cpu')
>
> Thanks,
> Alistair
>
> >
> >
> >> object_property_set_link(OBJECT(&s->soc), OBJECT(&s->ddr_ram),
> >> "ddr-ram", &error_abort);
> >> object_property_set_bool(OBJECT(&s->soc), s->secure, "secure",
> >> @@ -160,6 +162,10 @@ static void xlnx_zynqmp_init(XlnxZCU102 *s,
> >> MachineState *machine)
> >> arm_load_kernel(s->soc.boot_cpu_ptr, &xlnx_zcu102_binfo);
> >> }
> >>
> >> +const char *xlnx_zynqmp_valid_cpus[] = { ARM_CPU_TYPE_NAME("cortex-a53"),
> >> + NULL
> >> + };
> >> +
> >> static void xlnx_ep108_init(MachineState *machine)
> >> {
> >> XlnxZCU102 *s = EP108_MACHINE(machine);
> >> @@ -185,6 +191,8 @@ static void xlnx_ep108_machine_class_init(ObjectClass
> >> *oc, void *data)
> >> mc->block_default_type = IF_IDE;
> >> mc->units_per_default_bus = 1;
> >> mc->ignore_memory_transaction_failures = true;
> >> + mc->default_cpu_type = ARM_CPU_TYPE_NAME("cortex-a53");
> >> + mc->valid_cpu_types = xlnx_zynqmp_valid_cpus;
> >> }
> >>
> >> static const TypeInfo xlnx_ep108_machine_init_typeinfo = {
> >> @@ -240,6 +248,8 @@ static void xlnx_zcu102_machine_class_init(ObjectClass
> >> *oc, void *data)
> >> mc->block_default_type = IF_IDE;
> >> mc->units_per_default_bus = 1;
> >> mc->ignore_memory_transaction_failures = true;
> >> + mc->default_cpu_type = ARM_CPU_TYPE_NAME("cortex-a53");
> >> + mc->valid_cpu_types = xlnx_zynqmp_valid_cpus;
> >> }
> >>
> >> static const TypeInfo xlnx_zcu102_machine_init_typeinfo = {
> >> diff --git a/hw/arm/xlnx-zynqmp.c b/hw/arm/xlnx-zynqmp.c
> >> index 2b27daf51d..1bff099ec1 100644
> >> --- a/hw/arm/xlnx-zynqmp.c
> >> +++ b/hw/arm/xlnx-zynqmp.c
> >> @@ -133,13 +133,6 @@ static void xlnx_zynqmp_init(Object *obj)
> >> XlnxZynqMPState *s = XLNX_ZYNQMP(obj);
> >> int i;
> >>
> >> - for (i = 0; i < XLNX_ZYNQMP_NUM_APU_CPUS; i++) {
> >> - object_initialize(&s->apu_cpu[i], sizeof(s->apu_cpu[i]),
> >> - "cortex-a53-" TYPE_ARM_CPU);
> >> - object_property_add_child(obj, "apu-cpu[*]",
> >> OBJECT(&s->apu_cpu[i]),
> >> - &error_abort);
> >> - }
> >> -
> >> object_initialize(&s->gic, sizeof(s->gic), gic_class_name());
> >> qdev_set_parent_bus(DEVICE(&s->gic), sysbus_get_default());
> >>
> >> @@ -187,6 +180,14 @@ static void xlnx_zynqmp_realize(DeviceState *dev,
> >> Error **errp)
> >> qemu_irq gic_spi[GIC_NUM_SPI_INTR];
> >> Error *err = NULL;
> >>
> >> + /* We need to do this here to ensure the cpu_type property is set. */
> >> + for (i = 0; i < XLNX_ZYNQMP_NUM_APU_CPUS; i++) {
> >> + object_initialize(&s->apu_cpu[i], sizeof(s->apu_cpu[i]),
> >> + s->cpu_type);
> >> + object_property_add_child(OBJECT(dev), "apu-cpu[*]",
> >> OBJECT(&s->apu_cpu[i]),
> >> + &error_abort);
> >> + }
> >> +
> >> ram_size = memory_region_size(s->ddr_ram);
> >>
> >> /* Create the DDR Memory Regions. User friendly checks should happen
> >> at
> >> @@ -425,6 +426,7 @@ static void xlnx_zynqmp_realize(DeviceState *dev,
> >> Error **errp)
> >> }
> >>
> >> static Property xlnx_zynqmp_props[] = {
> >> + DEFINE_PROP_STRING("cpu-type", XlnxZynqMPState, cpu_type),
> >> DEFINE_PROP_STRING("boot-cpu", XlnxZynqMPState, boot_cpu),
> >> DEFINE_PROP_BOOL("secure", XlnxZynqMPState, secure, false),
> >> DEFINE_PROP_BOOL("virtualization", XlnxZynqMPState, virt, false),
> >> diff --git a/include/hw/arm/xlnx-zynqmp.h b/include/hw/arm/xlnx-zynqmp.h
> >> index 6eff81a995..5afb8de11e 100644
> >> --- a/include/hw/arm/xlnx-zynqmp.h
> >> +++ b/include/hw/arm/xlnx-zynqmp.h
> >> @@ -86,6 +86,7 @@ typedef struct XlnxZynqMPState {
> >> XlnxDPState dp;
> >> XlnxDPDMAState dpdma;
> >>
> >> + char *cpu_type;
> >> char *boot_cpu;
> >> ARMCPU *boot_cpu_ptr;
> >>
> >> --
> >> 2.11.0
> >>
> >
> > --
> > Eduardo
>
- [Qemu-devel] [PATCH v1 4/5] xilinx_zynq: : Specify the valid CPUs, (continued)
Message not available
- Re: [Qemu-devel] [PATCH v1 3/5] xlnx-zcu102: Specify the valid CPUs, Eduardo Habkost, 2017/10/03
- Re: [Qemu-devel] [PATCH v1 3/5] xlnx-zcu102: Specify the valid CPUs, Alistair Francis, 2017/10/03
- Re: [Qemu-devel] [PATCH v1 3/5] xlnx-zcu102: Specify the valid CPUs, Eduardo Habkost, 2017/10/03
- Re: [Qemu-devel] [PATCH v1 3/5] xlnx-zcu102: Specify the valid CPUs,
Igor Mammedov <=
- Re: [Qemu-devel] [PATCH v1 3/5] xlnx-zcu102: Specify the valid CPUs, Eduardo Habkost, 2017/10/04
- Re: [Qemu-devel] [PATCH v1 3/5] xlnx-zcu102: Specify the valid CPUs, Igor Mammedov, 2017/10/04
- Re: [Qemu-devel] [PATCH v1 3/5] xlnx-zcu102: Specify the valid CPUs, Eduardo Habkost, 2017/10/04
- Re: [Qemu-devel] [PATCH v1 3/5] xlnx-zcu102: Specify the valid CPUs, Alistair Francis, 2017/10/04
- Re: [Qemu-devel] [PATCH v1 3/5] xlnx-zcu102: Specify the valid CPUs, Igor Mammedov, 2017/10/05
- Re: [Qemu-devel] [PATCH v1 3/5] xlnx-zcu102: Specify the valid CPUs, Eduardo Habkost, 2017/10/05
- Re: [Qemu-devel] [PATCH v1 3/5] xlnx-zcu102: Specify the valid CPUs, Igor Mammedov, 2017/10/06
- Re: [Qemu-devel] [PATCH v1 3/5] xlnx-zcu102: Specify the valid CPUs, Eduardo Habkost, 2017/10/06
- Re: [Qemu-devel] [PATCH v1 3/5] xlnx-zcu102: Specify the valid CPUs, Alistair Francis, 2017/10/06
- Re: [Qemu-devel] [PATCH v1 3/5] xlnx-zcu102: Specify the valid CPUs, Igor Mammedov, 2017/10/09