On 10 May 2016 at 11:21, Marc Zyngier <[email protected]> wrote: > The GICv3 driver wrongly assumes that it runs on the non-secure > side of a secure-enabled system, while it could be on a system > with a single security state, or a GICv3 with GICD_CTLR.DS set. > > Either way, it is important to configure this properly, or > interrupts will simply not be delivered on this HW. > > Cc: [email protected] > Reported-by: Peter Maydell <[email protected]> > Signed-off-by: Marc Zyngier <[email protected]> > --- > It is getting a bit late for 4.6, so I plan to put this on top of > the 4.7 stuff, and let it trickle down to the stable trees (hence > the CC to stable).
Tested-by: Peter Maydell <[email protected]> (using a QEMU with GICv3 emulation, which is how I found this bug in the first place.) thanks -- PMM
