From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:52498) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZL8FY-00086r-UM for qemu-devel@nongnu.org; Fri, 31 Jul 2015 07:13:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZL8FU-0002Ym-53 for qemu-devel@nongnu.org; Fri, 31 Jul 2015 07:13:16 -0400 Received: from mail-vk0-f51.google.com ([209.85.213.51]:33155) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZL8FU-0002Yf-1o for qemu-devel@nongnu.org; Fri, 31 Jul 2015 07:13:12 -0400 Received: by vkgc186 with SMTP id c186so19905392vkg.0 for ; Fri, 31 Jul 2015 04:13:11 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <02bd01d0cb81$bace5b10$306b1130$@samsung.com> References: <1dbab1e73e54f0fca4d6d05d50986d2dd396f867.1437731107.git.p.fedin@samsung.com> <026901d0cb73$e4708000$ad518000$@samsung.com> <02bd01d0cb81$bace5b10$306b1130$@samsung.com> From: Peter Maydell Date: Fri, 31 Jul 2015 12:12:52 +0100 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [PATCH v7 5/6] Initial implementation of vGICv3 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Pavel Fedin Cc: Eric Auger , Marc Zyngier , Shlomo Pongratz , Shlomo Pongratz , QEMU Developers , Christoffer Dall On 31 July 2015 at 12:12, Pavel Fedin wrote: > Hello! > >> >> I intentionally put some tracing to these conditions. On my >> >> system KVM_DEV_ARM_VGIC_GRP_NR_IRQS is supported and >> >> KVM_DEV_ARM_VGIC_CTRL_INIT is not. So will it always be this way? >> > >> > That is weird. I thought that the kernel devs had agreed that all >> > new VGIC code should require explicit initialization (ie that >> > lazy init-on-first-time-it's-needed was only there for legacy >> > guests and the old GICv2). The lazy-init stuff was a big source >> > of bugs where things weren't inited at the point where you >> > expected, which is why it should have gone away... >> >> I just checked with Marc, and he agreed that all kernels >> with GICv3 support should support VGIC_CTRL_INIT. What kernel >> are you running? > > v3.18 with backported GICv3 support. It is a choice of our > HW vendor and their current official kernel. Sounds like their backporting is buggy, then. They need to fix it, I don't think we need to support broken branches in QEMU. thanks -- PMM