From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marc Zyngier Subject: Re: kvm-unit-tests gicv2 cases fail Date: Thu, 01 Nov 2018 10:25:54 +0000 Message-ID: <86a7mt2ix9.wl-marc.zyngier@arm.com> References: <20181101101048.GJ12057@e113682-lin.lund.arm.com> Mime-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from localhost (localhost [127.0.0.1]) by mm01.cs.columbia.edu (Postfix) with ESMTP id 240404A2B2 for ; Thu, 1 Nov 2018 06:26:01 -0400 (EDT) Received: from mm01.cs.columbia.edu ([127.0.0.1]) by localhost (mm01.cs.columbia.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8n+CGWqWXzlt for ; Thu, 1 Nov 2018 06:26:00 -0400 (EDT) Received: from foss.arm.com (foss.arm.com [217.140.101.70]) by mm01.cs.columbia.edu (Postfix) with ESMTP id E0B184A1E5 for ; Thu, 1 Nov 2018 06:25:59 -0400 (EDT) In-Reply-To: <20181101101048.GJ12057@e113682-lin.lund.arm.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kvmarm-bounces@lists.cs.columbia.edu Sender: kvmarm-bounces@lists.cs.columbia.edu To: Christoffer Dall Cc: kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org List-Id: kvmarm@lists.cs.columbia.edu [Thanks Christoffer for cc'ing me] On Thu, 01 Nov 2018 10:10:48 +0000, Christoffer Dall wrote: > > On Thu, Oct 18, 2018 at 05:17:57PM +0800, Li Zhang wrote: > > Hi, > > > > I run kvm-units-test on ARM server(QDF2400), but gicv2-ipi, > > gicv2-active cases fail. > > I didn't think QDF2400 has GICv2 on GICv3 support? > > Do the test cases fail or are they reported as skipped? > > > By debuging kvm-unit-tests source code, I found that interrupt is not > > handled. do_handle_exception is not called. > > > > By looking into KVM source code, it has GICv2 emulation on GICv3 support. > > I've tried a lot of kernel versions, from v4.12~v4.19 in mainline, > > these cases always fail. > > Is it possible that hardware/software disables this? Most implementations do not have the v2 compatibility interface, and nobody really needs it. This is a convenient way to run older VMs that do not know about GICv3 (32bit VMs, for example), but that's in no way a common setup. > > > > It seems that GICv2 is a little old for ARM server, I am confused when > > we can use it. > > Do we need to care about these cases? > > > > I don't think you need to care. I believe Marc has run the > GICv2-on-GICv3 tests on his supported platforms with recent > kvm-unit-tests and other have reported succes as well. Here you go (on my Chromebook running 4.18): PASS gicv2-ipi (3 tests) PASS gicv2-mmio (17 tests) PASS gicv2-mmio-up (17 tests) PASS gicv2-mmio-3p (17 tests) PASS gicv3-ipi (3 tests) PASS gicv2-active (1 tests) PASS gicv3-active (1 tests) Thanks, M. -- Jazz is not dead, it just smell funny.