On 2016年06月15日 18:10, Peter Maydell wrote: > On 15 June 2016 at 11:06, Peter Maydell <peter.mayd...@linaro.org> wrote: >> > On 15 June 2016 at 10:20, Andrew Jones <drjo...@redhat.com> wrote: >>> >> There may be a bug in the freebsd kernel. Maybe they need the equivalent >>> >> of Linux's 7c9b973061 "irqchip/gic-v3: Configure all interrupts as >>> >> non-secure Group-1". You could add the hack back that was in the initial >>> >> posting of this series to see if that "fixes" things. >> > >> > I agree it's possible this is a freebsd bug, but the hack patch >> > won't help here because we're booting via EFI. > A quick scan through http://fxr.watson.org/fxr/source/arm64/arm64/gic_v3.c > doesn't seem to show it setting the IGROUPR registers anywhere, > so it probably is a guest bug. (You can use "-d 'trace:gicv3*'" to > enable the tracepoints for the GIC which would let you check whether > the guest ever tries to write to the group config registers.) I'll try tomorrow. By the way, if we disable secure extension, will the problem disappear?
Thanks, -- Shannon
