From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:37840)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <p.fedin@samsung.com>) id 1Zouml-0002I6-QU
	for qemu-devel@nongnu.org; Wed, 21 Oct 2015 10:54:40 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <p.fedin@samsung.com>) id 1Zoumg-0006aX-0n
	for qemu-devel@nongnu.org; Wed, 21 Oct 2015 10:54:39 -0400
Received: from mailout4.w1.samsung.com ([210.118.77.14]:54015)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <p.fedin@samsung.com>) id 1Zoumf-0006aF-RO
	for qemu-devel@nongnu.org; Wed, 21 Oct 2015 10:54:33 -0400
Received: from eucpsbgm1.samsung.com (unknown [203.254.199.244])
	by mailout4.w1.samsung.com
	(Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5
	2014)) with ESMTP id <0NWK00J4OS2V9V70@mailout4.w1.samsung.com> for
	qemu-devel@nongnu.org; Wed, 21 Oct 2015 15:54:31 +0100 (BST)
From: Pavel Fedin <p.fedin@samsung.com>
References: <1445361732-16257-1-git-send-email-shlomopongratz@gmail.com>
	<1445361732-16257-7-git-send-email-shlomopongratz@gmail.com>
	<014301d10bfe$20c00970$62401c50$@samsung.com>
	<CAHzK-V0zNYeYDYn6thGW08JJDVf7AQphxUtL6ud9i04TG1iLLQ@mail.gmail.com>
	<015801d10c02$1c60d130$55227390$@samsung.com>
	<CAHzK-V2WagbPU-kB0r=g1a0Gb0B+4x1Q44+daWzaYBOF4i2kmg@mail.gmail.com>
	<016c01d10c07$3b156fa0$b1404ee0$@samsung.com>
	<CAHzK-V2=Wm_WyrKu+YegEzRcDfGjLQnnembYp3fK83iESjA3nA@mail.gmail.com>
	<019c01d10c0c$83292e30$897b8a90$@samsung.com>
	<CAHzK-V04Sb_N57BzJkQW5dRnF4CS+ocjWz9ja+pxPvLmVyB7gw@mail.gmail.com>
	<01ba01d10c0e$9ebbfa90$dc33efb0$@samsung.com>
	<CAFEAcA8iKNeBCNdoDdTEwwvhdq=zZU6t97=XcDkxP=ZfC0ErFg@mail.gmail.com>
In-reply-to: <CAFEAcA8iKNeBCNdoDdTEwwvhdq=zZU6t97=XcDkxP=ZfC0ErFg@mail.gmail.com>
Date: Wed, 21 Oct 2015 17:54:29 +0300
Message-id: <01c701d10c10$642bb0d0$2c831270$@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 RFC V5 6/9] hw/intc: arm_gicv3_spi_its
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>, 'Shlomo Pongratz' <shlomo.pongratz@huawei.com>, 'Shlomo Pongratz' <shlomopongratz@gmail.com>, 'QEMU Developers' <qemu-devel@nongnu.org>, 'Shannon Zhao' <shannon.zhao@linaro.org>, 'Ashok Kumar' <ashoks@broadcom.com>, 'Igor Mammedov' <imammedo@redhat.com>

 Hello!

> For QEMU we could in theory do either; I was leaning towards
> direct connection just because on the KVM side the in-kernel
> GIC isn't going to separate them out as two distinct things.

 I'd say this is not entirely true. With KVM you still can have vGIC =
without vITS. Just don't set KVM_VGIC_V3_ADDR_TYPE_ITS and that's it. =
The only thing linked in is LPI support. With KVM you cannot have LPIs =
without vITS. Neither you can directly inject LPIs.
 So, in-kernel ITS is also optional.

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