On Fri, 30 Aug 2024 at 09:05, Edgar E. Iglesias <edgar.igles...@gmail.com> wrote: > > On Thu, Aug 29, 2024 at 01:50:02PM +0100, Peter Maydell wrote: > > On Wed, 28 Aug 2024 at 01:51, Sebastian Huber > > <sebastian.hu...@embedded-brains.de> wrote: > > > > > > The system supports the Security Extensions (core and GIC). This change > > > is > > > necessary to run tests which pass on the real hardware. > > > > > > Signed-off-by: Sebastian Huber <sebastian.hu...@embedded-brains.de> > > > > (Added the maintainers to cc.) > > > > Does the system have any secure-only devices, RAM, etc? > > Yes, on real HW there are but I don't think we've modelled any of it yet. > There's TZ both on the SoC and also ability to create FPGA logic that > can issue secure/non-secure transactions. Here's an overview: > https://docs.amd.com/v/u/en-US/ug1019-zynq-trustzone > > The primary use-case for the upstream Zynq-7000 QEMU models has historically > been to run the Open Source SW stack from Linux (some times from u-boot) > and up. It's important that we don't break that. > > So as long as we add additional support without breaking direct Linux > boots, I think it's OK to incrementally enable missing pieces even > if there's not yet coherent support for firmware boot. > > In this case, IIUC, when doing direct Linux boot, TYPE_ARM_LINUX_BOOT_IF > will take care of the GIC setup for us.
Yep, that's the way it's supposed to work. OK, let's enable this; it's the beginning of the release cycle for 9.2 so there's plenty of time to fix any problem that might get reported to us before release. Applied to target-arm.next, thanks. -- PMM
