Expose the secure property to the machine
cover Expose the secure property to the machine
The EL2 and EL3 work is working well now and interanlly we now have tests that expect to start in EL3 and transition through EL2 to EL1. To make this easy to run let's expose the secure property to the machine and then use that to enable EL2.
This series also does some machine/name tidying up and makes the first move to deprecating the EP108 machine, which was just an early access development board.
Alistair Francis (5):
xlnx-ep108: Rename to ZCU102
xlnx-zcu102: Manually create the machines
xlnx-zcu102: Add a machine level secure property
xlnx-zynqmp: Allow the secure prop to enable EL2
xlnx-zcu102: Mark the EP108 machine as deprecated
hw/arm/Makefile.objs | 2 +-
hw/arm/{xlnx-ep108.c => xlnx-zcu102.c} | 131 ++++++++++++++++++++++++++++-----
hw/arm/xlnx-zynqmp.c | 2 +-
3 files changed, 114 insertions(+), 21 deletions(-)
rename hw/arm/{xlnx-ep108.c => xlnx-zcu102.c} (51%)Signature · 1 line
2.11.0
PATCH 2/5 xlnx-zcu102: Manually create the machines
In preperation for future work let's manually create the Xilnx machines. This will allow us to set properties for the machines in the future.
---
hw/arm/xlnx-zcu102.c | 75 +++++++++++++++++++++++++++++++++++++++++++++++----- 1 file changed, 68 insertions(+), 7 deletions(-)
hw/arm/xlnx-zcu102.c +68 -7
@@ -26,15 +26,25 @@#include "qemu/log.h" typedef struct XlnxZCU102 { + +MachineState parent_obj; +XlnxZynqMPState soc;MemoryRegion ddr_ram; }XlnxZCU102 ; +#define TYPE_ZCU102_MACHINE MACHINE_TYPE_NAME("xlnx-zcu102") +#define ZCU102_MACHINE (obj) \ + OBJECT_CHECK(XlnxZCU102, (obj), TYPE_ZCU102_MACHINE) + +#define TYPE_EP108_MACHINE MACHINE_TYPE_NAME("xlnx-ep108") +#define EP108_MACHINE (obj) \ + OBJECT_CHECK(XlnxZCU102, (obj), TYPE_EP108_MACHINE) +static struct arm_boot_info xlnx_zcu102_binfo; -static void xlnx_zcu102_init (MachineState *machine) +static void xlnx_zynqmp_init (XlnxZCU102 *s,MachineState *machine) { -XlnxZCU102 *s =g_new0 (XlnxZCU102,1 );int i;uint64_t ram_size = machine->ram_size;
@@ -116,22 +126,73 @@ static void xlnx_zcu102_init(MachineState *machine)arm_load_kernel (s->soc.boot_cpu_ptr, &xlnx_zcu102_binfo); } -static void xlnx_ep108_machine_init (MachineClass *mc) +static void xlnx_ep108_init (MachineState *machine) { +XlnxZCU102 *s =EP108_MACHINE (machine); + +xlnx_zynqmp_init (s, machine); +} + +static void xlnx_ep108_machine_instance_init (Object *obj) +{ +} + +static void xlnx_ep108_machine_class_init (ObjectClass *oc,void *data) +{ +MachineClass *mc =MACHINE_CLASS (oc); + mc->desc ="Xilinx ZynqMP EP108 board" ; - mc->init = xlnx_zcu102_init; + mc->init = xlnx_ep108_init; mc->block_default_type =IF_IDE ; mc->units_per_default_bus =1 ; } -DEFINE_MACHINE("xlnx-ep108", xlnx_ep108_machine_init) +static const TypeInfo xlnx_ep108_machine_init_typeinfo = { + .name =MACHINE_TYPE_NAME ("xlnx-ep108" ), + .parent =TYPE_MACHINE , + .class_init = xlnx_ep108_machine_class_init, + .instance_init = xlnx_ep108_machine_instance_init, + .instance_size =sizeof (XlnxZCU102), +}; + +static void xlnx_ep108_machine_init_register_types (void ) +{ +type_register_static (&xlnx_ep108_machine_init_typeinfo); +} + +static void xlnx_zcu102_init (MachineState *machine) +{ +XlnxZCU102 *s =ZCU102_MACHINE (machine); + +xlnx_zynqmp_init (s, machine); +} -static void xlnx_zcu102_machine_init (MachineClass *mc) +static void xlnx_zcu102_machine_instance_init (Object *obj) { +} + +static void xlnx_zcu102_machine_class_init (ObjectClass *oc,void *data) +{ +MachineClass *mc =MACHINE_CLASS (oc); + mc->desc ="Xilinx ZynqMP ZCU102 board" ; mc->init = xlnx_zcu102_init; mc->block_default_type =IF_IDE ; mc->units_per_default_bus =1 ; } -DEFINE_MACHINE ("xlnx-zcu102" , xlnx_zcu102_machine_init) +static const TypeInfo xlnx_zcu102_machine_init_typeinfo = { + .name =MACHINE_TYPE_NAME ("xlnx-zcu102" ), + .parent =TYPE_MACHINE , + .class_init = xlnx_zcu102_machine_class_init, + .instance_init = xlnx_zcu102_machine_instance_init, + .instance_size =sizeof (XlnxZCU102), +}; + +static void xlnx_zcu102_machine_init_register_types (void ) +{ +type_register_static (&xlnx_zcu102_machine_init_typeinfo); +} + +type_init (xlnx_zcu102_machine_init_register_types) +type_init (xlnx_ep108_machine_init_register_types)
Signature · 1 line
2.11.0
PATCH 4/5 xlnx-zynqmp: Allow the secure prop to enable EL2
In reply to Alistair FrancisIf the user sets the secure property to true we want to enalbe both EL2 and EL3.
---
hw/arm/xlnx-zynqmp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
hw/arm/xlnx-zynqmp.c +1 -1
@@ -260,7 +260,7 @@ static void xlnx_zynqmp_realize(DeviceState *dev, Error **errp)object_property_set_bool (OBJECT (&s->apu_cpu[i]), s->secure,"has_el3" ,NULL );object_property_set_bool (OBJECT (&s->apu_cpu[i]), - false,"has_el2" ,NULL ); + s->secure,"has_el2" ,NULL );object_property_set_int (OBJECT (&s->apu_cpu[i]),GIC_BASE_ADDR ,"reset-cbar" , &error_abort); object_property_set_bool(OBJECT(&s->apu_cpu[i]), true, "realized",
Signature · 1 line
2.11.0
PATCH 5/5 xlnx-zcu102: Mark the EP108 machine as deprecated
In reply to Alistair FrancisThe EP108 is the same as the ZCU102, mark it as deprecated as we don't need two machines.
---
hw/arm/xlnx-zcu102.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
hw/arm/xlnx-zcu102.c +1 -1
@@ -163,7 +163,7 @@ static void xlnx_ep108_machine_class_init(ObjectClass *oc, void *data) {MachineClass *mc =MACHINE_CLASS (oc); - mc->desc ="Xilinx ZynqMP EP108 board" ; + mc->desc ="Xilinx ZynqMP EP108 board (Deprecated, please use xlnx-zcu102)" ; mc->init = xlnx_ep108_init; mc->block_default_type =IF_IDE ; mc->units_per_default_bus =1 ;
Signature · 1 line
2.11.0
Quoted 8 lines · Alistair Francis
The EL2 and EL3 work is working well now and interanlly we now have tests that expect to start in EL3 and transition through EL2 to EL1. To make this easy to run let's expose the secure property to the machine and then use that to enable EL2.
This series also does some machine/name tidying up and makes the first move to deprecating the EP108 machine, which was just an early access development board.
Hi Alistair,
Reconsidering this, I tend to agree that we're probably better off with EL2/no-GICv2-virt compared to the possible confusiong of having EL2 without GICv2-virt..
But I wonder if we should have similar options as the virt machine? I.e, a virtualization option to enable EL2.
Cheers,
Edgar
Quoted 17 lines
Alistair Francis (5):
xlnx-ep108: Rename to ZCU102
xlnx-zcu102: Manually create the machines
xlnx-zcu102: Add a machine level secure property
xlnx-zynqmp: Allow the secure prop to enable EL2
xlnx-zcu102: Mark the EP108 machine as deprecatedhw/arm/Makefile.objs | 2 +- hw/arm/{xlnx-ep108.c => xlnx-zcu102.c} | 131 ++++++++++++++++++++++++++++----- hw/arm/xlnx-zynqmp.c | 2 +- 3 files changed, 114 insertions(+), 21 deletions(-) rename hw/arm/{xlnx-ep108.c => xlnx-zcu102.c} (51%)Signature · 1 line
2.11.0
Re: [Qemu-devel] [PATCH v1 2/5] xlnx-zcu102: Manually create the machines
In reply to Alistair FrancisQuoted 14 lines · Alistair Francis
In preperation for future work let's manually create the Xilnx machines. This will allow us to set properties for the machines in the future.
Signed-off-by Alistair Francis <[email protected]>---
hw/arm/xlnx-zcu102.c | 75 +++++++++++++++++++++++++++++++++++++++++++++++----- 1 file changed, 68 insertions(+), 7 deletions(-)hw/arm/xlnx-zcu102.c +0
-0
hw/arm/xlnx-zcu102.c line 29
Quoted 4 lines
hw/arm/xlnx-zcu102.c +1
-0@@ -26,15 +26,25 @@#include "qemu/log.h" typedef struct XlnxZCU102 { +
Looks like a stray newline here.
Quoted 105 lines
hw/arm/xlnx-zcu102.c +67
-7+MachineState parent_obj; +XlnxZynqMPState soc;MemoryRegion ddr_ram; } XlnxZCU102; +#define TYPE_ZCU102_MACHINE MACHINE_TYPE_NAME("xlnx-zcu102") +#define ZCU102_MACHINE (obj) \ + OBJECT_CHECK(XlnxZCU102, (obj), TYPE_ZCU102_MACHINE) + +#define TYPE_EP108_MACHINE MACHINE_TYPE_NAME("xlnx-ep108") +#define EP108_MACHINE (obj) \ + OBJECT_CHECK(XlnxZCU102, (obj), TYPE_EP108_MACHINE) +static struct arm_boot_info xlnx_zcu102_binfo; -static void xlnx_zcu102_init (MachineState *machine) +static void xlnx_zynqmp_init (XlnxZCU102 *s,MachineState *machine) { -XlnxZCU102 *s =g_new0 (XlnxZCU102,1 );int i;uint64_t ram_size = machine->ram_size;@@ -116,22 +126,73 @@ static void xlnx_zcu102_init(MachineState *machine)arm_load_kernel (s->soc.boot_cpu_ptr, &xlnx_zcu102_binfo); } -static void xlnx_ep108_machine_init (MachineClass *mc) +static void xlnx_ep108_init (MachineState *machine) { +XlnxZCU102 *s =EP108_MACHINE (machine); + +xlnx_zynqmp_init (s, machine); +} + +static void xlnx_ep108_machine_instance_init (Object *obj) +{ +} + +static void xlnx_ep108_machine_class_init (ObjectClass *oc,void *data) +{ +MachineClass *mc =MACHINE_CLASS (oc); + mc->desc ="Xilinx ZynqMP EP108 board" ; - mc->init = xlnx_zcu102_init; + mc->init = xlnx_ep108_init; mc->block_default_type =IF_IDE ; mc->units_per_default_bus =1 ; } -DEFINE_MACHINE("xlnx-ep108", xlnx_ep108_machine_init) +static const TypeInfo xlnx_ep108_machine_init_typeinfo = { + .name =MACHINE_TYPE_NAME ("xlnx-ep108" ), + .parent =TYPE_MACHINE , + .class_init = xlnx_ep108_machine_class_init, + .instance_init = xlnx_ep108_machine_instance_init, + .instance_size =sizeof (XlnxZCU102), +}; + +static void xlnx_ep108_machine_init_register_types (void ) +{ +type_register_static (&xlnx_ep108_machine_init_typeinfo); +} + +static void xlnx_zcu102_init (MachineState *machine) +{ +XlnxZCU102 *s =ZCU102_MACHINE (machine); + +xlnx_zynqmp_init (s, machine); +} -static void xlnx_zcu102_machine_init (MachineClass *mc) +static void xlnx_zcu102_machine_instance_init (Object *obj) { +} + +static void xlnx_zcu102_machine_class_init (ObjectClass *oc,void *data) +{ +MachineClass *mc =MACHINE_CLASS (oc); + mc->desc ="Xilinx ZynqMP ZCU102 board" ; mc->init = xlnx_zcu102_init; mc->block_default_type =IF_IDE ; mc->units_per_default_bus =1 ; } -DEFINE_MACHINE ("xlnx-zcu102" , xlnx_zcu102_machine_init) +static const TypeInfo xlnx_zcu102_machine_init_typeinfo = { + .name =MACHINE_TYPE_NAME ("xlnx-zcu102" ), + .parent =TYPE_MACHINE , + .class_init = xlnx_zcu102_machine_class_init, + .instance_init = xlnx_zcu102_machine_instance_init, + .instance_size =sizeof (XlnxZCU102), +}; + +static void xlnx_zcu102_machine_init_register_types (void ) +{ +type_register_static (&xlnx_zcu102_machine_init_typeinfo); +} + +type_init (xlnx_zcu102_machine_init_register_types) +type_init (xlnx_ep108_machine_init_register_types)Signature · 1 line
2.11.0
Quoted 10 lines · Edgar E. Iglesias
Quoted 8 lines · Alistair Francis
The EL2 and EL3 work is working well now and interanlly we now have tests that expect to start in EL3 and transition through EL2 to EL1. To make this easy to run let's expose the secure property to the machine and then use that to enable EL2.
This series also does some machine/name tidying up and makes the first move to deprecating the EP108 machine, which was just an early access development board.
Quoted 8 lines
Hi Alistair,
Reconsidering this, I tend to agree that we're probably better off with EL2/no-GICv2-virt compared to the possible confusiong of having EL2 without GICv2-virt..
But I wonder if we should have similar options as the virt machine? I.e, a virtualization option to enable EL2.
That's fine with me.
Just to clarify do you think we should keep the secure option for EL3 and add a virt option for EL2?
Thanks,
Alistair
Quoted 22 lines
Cheers,
EdgarQuoted 17 lines
Alistair Francis (5):
xlnx-ep108: Rename to ZCU102
xlnx-zcu102: Manually create the machines
xlnx-zcu102: Add a machine level secure property
xlnx-zynqmp: Allow the secure prop to enable EL2
xlnx-zcu102: Mark the EP108 machine as deprecatedhw/arm/Makefile.objs | 2 +- hw/arm/{xlnx-ep108.c => xlnx-zcu102.c} | 131 ++++++++++++++++++++++++++++----- hw/arm/xlnx-zynqmp.c | 2 +- 3 files changed, 114 insertions(+), 21 deletions(-) rename hw/arm/{xlnx-ep108.c => xlnx-zcu102.c} (51%)--
2.11.0
Quoted 18 lines · Alistair Francis
Quoted 16 lines · Edgar E. Iglesias
Quoted 8 lines · Alistair Francis
The EL2 and EL3 work is working well now and interanlly we now have tests that expect to start in EL3 and transition through EL2 to EL1. To make this easy to run let's expose the secure property to the machine and then use that to enable EL2.
This series also does some machine/name tidying up and makes the first move to deprecating the EP108 machine, which was just an early access development board.
Hi Alistair,
Reconsidering this, I tend to agree that we're probably better off with EL2/no-GICv2-virt compared to the possible confusiong of having EL2 without GICv2-virt..
Quoted 7 lines
Quoted 2 lines
But I wonder if we should have similar options as the virt machine? I.e, a virtualization option to enable EL2.
That's fine with me.
Just to clarify do you think we should keep the secure option for EL3 and add a virt option for EL2?
I think unless you have a really strong reason to be different (eg back-compat with existing guests) then following what the 'virt' board does for machine options is probably going to be least confusing. NB that that does include letting you specify some combos that don't work, like gicv2 + virt...
(We should really get round to implementing virt support in the GICv2, though.)
thanks
-- PMM