From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:47139)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <p.fedin@samsung.com>) id 1YvSoF-00044K-FM
	for qemu-devel@nongnu.org; Thu, 21 May 2015 11:55:00 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <p.fedin@samsung.com>) id 1YvSoC-0001sG-7l
	for qemu-devel@nongnu.org; Thu, 21 May 2015 11:54:59 -0400
Received: from mailout4.w1.samsung.com ([210.118.77.14]:32347)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <p.fedin@samsung.com>) id 1YvSoC-0001ry-03
	for qemu-devel@nongnu.org; Thu, 21 May 2015 11:54:56 -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 <0NOP004NEIVHVSC0@mailout4.w1.samsung.com> for
	qemu-devel@nongnu.org; Thu, 21 May 2015 16:54:53 +0100 (BST)
From: Pavel Fedin <p.fedin@samsung.com>
References: <1430921082-16779-1-git-send-email-shlomopongratz@gmail.com>
	<1430921082-16779-2-git-send-email-shlomopongratz@gmail.com>
In-reply-to: <1430921082-16779-2-git-send-email-shlomopongratz@gmail.com>
Date: Thu, 21 May 2015 18:54:51 +0300
Message-id: <000601d093de$79adf210$6d09d630$@samsung.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-language: ru
Subject: Re: [Qemu-devel] [PATCH RFC V2 1/4] Use Aff1 with mpidr
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: shlomopongratz@gmail.com, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, 'Ashok Kumar' <ashoks@broadcom.com>, 'Shlomo Pongratz' <shlomo.pongratz@huawei.com>

 Hello!

> In order to support up to 128 cores with GIC-500 (GICv3 implementation)
> affinity1 must be used. GIC-500 support up to 32 clusters with up to
> 8 cores in a cluster. So for example, if one wishes to have 16 cores,
> the options are: 2 clusters of 8 cores each, 4 clusters with 4 cores each

 I have found one more concern. Are you really sure about this scheme ? I am currently
experimenting with KVM, and it seems to have 16 CPUs per cluster, at least on my machine.
Actually i suggest that KVM inherits the mapping from the host. Can we do the same?
 I will take a look at kvmtool, how it determines these IDs. But hardcoded scheme is
definitely wrong.

 Cc'ed Ashok because he might also be interested.

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