From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:51864)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <p.fedin@samsung.com>) id 1ZL8EZ-0007CM-GY
	for qemu-devel@nongnu.org; Fri, 31 Jul 2015 07:12:16 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <p.fedin@samsung.com>) id 1ZL8EU-0002Ab-CE
	for qemu-devel@nongnu.org; Fri, 31 Jul 2015 07:12:15 -0400
Received: from mailout4.w1.samsung.com ([210.118.77.14]:57920)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <p.fedin@samsung.com>) id 1ZL8EU-00027G-6R
	for qemu-devel@nongnu.org; Fri, 31 Jul 2015 07:12:10 -0400
Received: from eucpsbgm2.samsung.com (unknown [203.254.199.245])
	by mailout4.w1.samsung.com
	(Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5
	2014)) with ESMTP id <0NSC007Q5N44VQ80@mailout4.w1.samsung.com> for
	qemu-devel@nongnu.org; Fri, 31 Jul 2015 12:12:05 +0100 (BST)
From: Pavel Fedin <p.fedin@samsung.com>
References: <cover.1437731107.git.p.fedin@samsung.com>
	<1dbab1e73e54f0fca4d6d05d50986d2dd396f867.1437731107.git.p.fedin@samsung.com>
	<CAFEAcA_pyW-0QaM-0R7WGNM=OFB7iHimtnZvb2+wDbCYWY9GXw@mail.gmail.com>
	<026901d0cb73$e4708000$ad518000$@samsung.com>
	<CAFEAcA-UzK5+qbAZZRnpaLrqMV6w0KzRGtfSnui7QjWcfshWVQ@mail.gmail.com>
	<CAFEAcA-Q1q1odtBET_7x7Ajd5mbjqsEbXnHu5KxTDVVcKzPSMQ@mail.gmail.com>
In-reply-to: <CAFEAcA-Q1q1odtBET_7x7Ajd5mbjqsEbXnHu5KxTDVVcKzPSMQ@mail.gmail.com>
Date: Fri, 31 Jul 2015 14:12:02 +0300
Message-id: <02bd01d0cb81$bace5b10$306b1130$@samsung.com>
MIME-version: 1.0
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: quoted-printable
Content-language: ru
Subject: Re: [Qemu-devel] [PATCH v7 5/6] Initial implementation of vGICv3
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: 'Peter Maydell' <peter.maydell@linaro.org>
Cc: 'Eric Auger' <eric.auger@linaro.org>, 'Marc Zyngier' <marc.zyngier@arm.com>, 'Shlomo Pongratz' <shlomo.pongratz@huawei.com>, 'Shlomo Pongratz' <shlomopongratz@gmail.com>, 'QEMU Developers' <qemu-devel@nongnu.org>, 'Christoffer Dall' <christoffer.dall@linaro.org>

 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...
>=20
> 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.

Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia