From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42934) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bFdW2-0002Vr-VQ for qemu-devel@nongnu.org; Wed, 22 Jun 2016 04:28:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bFdVy-0004lV-TN for qemu-devel@nongnu.org; Wed, 22 Jun 2016 04:28:06 -0400 Received: from szxga02-in.huawei.com ([119.145.14.65]:47734) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bFdVy-0004jq-1t for qemu-devel@nongnu.org; Wed, 22 Jun 2016 04:28:02 -0400 Message-ID: <576A4BF7.4050501@huawei.com> Date: Wed, 22 Jun 2016 16:27:35 +0800 From: Shannon Zhao MIME-Version: 1.0 References: <5761178F.60004@huawei.com> <20160621144555.zsvsukja7wrxxkvi@hawk.localdomain> <20160621151202.hbwpqyvmbnno3yfy@hawk.localdomain> <20160621171557.uq6ellpqom43kanz@hawk.localdomain> <20160621171813.hbzbzx3ojys2tkts@hawk.localdomain> <5c504e1b-f311-272a-724f-2182349c3cd1@redhat.com> <5769ED05.2050409@huawei.com> <20160622074342.navvazli3ekal3sf@hawk.localdomain> In-Reply-To: <20160622074342.navvazli3ekal3sf@hawk.localdomain> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v3 00/20] GICv3 emulation List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Andrew Jones Cc: Peter Maydell , Laszlo Ersek , Patch Tracking , Shlomo Pongratz , Shlomo Pongratz , Ard Biesheuvel , Pavel Fedin , QEMU Developers , Shannon Zhao , Christoffer Dall On 2016/6/22 15:43, Andrew Jones wrote: > On Wed, Jun 22, 2016 at 09:42:29AM +0800, Shannon Zhao wrote: >> > >> > >> > On 2016/6/22 3:53, Peter Maydell wrote: >>> > > On 21 June 2016 at 20:45, Laszlo Ersek wrote: >>>>> > >> > On 06/21/16 19:21, Peter Maydell wrote: >>>>>>> > >>> >> and add a note I forgot to mention: my primary hypothesis is that >>>>>>> > >>> >> the problem here is "guest does not write to the GICD_IGROUPR and >>>>>>> > >>> >> GICR_IGROUPR registers to program the interrupts it's using as >>>>>>> > >>> >> group 1, but still expects to get IRQs rather than FIQs". >>>>> > >> > >>>>> > >> > ... and it (or whatever else is the root cause) seems to manifest in >>>>> > >> > either the Stall() UEFI boot service, or in UEFI timer events. (This >>>>> > >> > seems to follow from the last debug log entry from Shannon: >>>>> > >> > >>>>> > >> > [Bds]BdsWait(3)..Zzzz... >>>>> > >> > ) >>>>> > >> > >>>>> > >> > ... Just to make it clear: does it reproduce with KVM? Or is that >>>>> > >> > untested perhaps (due to lack of GICv3 hardware e.g.)? >>> > > Upthread Shannon said it worked with KVM enabled. Note that >>> > > KVM's GICv3 emulation is incorrect in that it does not support >>> > > interrupt groups, so all interrupt groups are Group 1 and >>> > > generate IRQ even if the guest doesn't do anything to >>> > > configure them. >> > It does work with KVM enabled. It also works with UEFI and the upstream >> > linux kernel while it doesn't work with UEFI and a FreeBSD guest since >> > the FreeBSD doesn't correctly set the IGROUPR, I think. > Doesn't appear to be FreeBSD specific, as I'm using a Linux kernel and > can reproduce. Besides, it doesn't even make it to grub. > >> > >> > I can't find the commit ID of the UEFI I use but I used the upsream >> > codes of June 15. >> > Andrew, I suggest you use the QEMU mainline which includes the GICv3 >> > emulation and the guest kernel with the commit 7c9b973061. > Yeah, I hadn't noticed that gicv3 made it to mainline. I've switched > to that now. My guest kernel does have 7c9b973061 (I backported it to > the RHELSA kernel) I just used a new UEFI binary which is built on 8f88f02 and the upstream linux kernel. It boots as well. Could you try the upstream linux kernel? Thanks, -- Shannon