From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43112) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bDBOr-0003f1-Lp for qemu-devel@nongnu.org; Wed, 15 Jun 2016 10:02:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bDBOl-0007Ir-UR for qemu-devel@nongnu.org; Wed, 15 Jun 2016 10:02:33 -0400 Received: from mail-pf0-x22b.google.com ([2607:f8b0:400e:c00::22b]:34498) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bDBOk-0007In-Kw for qemu-devel@nongnu.org; Wed, 15 Jun 2016 10:02:27 -0400 Received: by mail-pf0-x22b.google.com with SMTP id 62so9218746pfd.1 for ; Wed, 15 Jun 2016 07:02:26 -0700 (PDT) References: <1465915112-29272-1-git-send-email-peter.maydell@linaro.org> <5761178F.60004@huawei.com> <20160615092023.fk2vfowubdk6nhmk@hawk.localdomain> From: Shannon Zhao Message-ID: <57615FE8.4050303@linaro.org> Date: Wed, 15 Jun 2016 22:02:16 +0800 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [Qemu-devel] [PATCH v3 00/20] GICv3 emulation List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell , Andrew Jones Cc: Shannon Zhao , QEMU Developers , Patch Tracking , Shlomo Pongratz , Shlomo Pongratz , Pavel Fedin , Christoffer Dall On 2016年06月15日 18:10, Peter Maydell wrote: > On 15 June 2016 at 11:06, Peter Maydell wrote: >> > On 15 June 2016 at 10:20, Andrew Jones 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