Re: [Qemu-devel] [PATCH v1 0/5] Expose the secure property to the machine

["Edgar E. Iglesias" <edgar.iglesias@xilinx.com>]

On Thu, Aug 17, 2017 at 11:51:59AM -0700, Alistair Francis wrote:
> 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


> 
> 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%)
> 
> -- 
> 2.11.0
>