From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58131) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YxfgT-0007XD-Ml for qemu-devel@nongnu.org; Wed, 27 May 2015 14:04:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YxfgP-0004r4-G9 for qemu-devel@nongnu.org; Wed, 27 May 2015 14:04:05 -0400 Received: from mailout4.w1.samsung.com ([210.118.77.14]:40245) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YxfgP-0004q9-A2 for qemu-devel@nongnu.org; Wed, 27 May 2015 14:04:01 -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 <0NP000IDSSUKBY70@mailout4.w1.samsung.com> for qemu-devel@nongnu.org; Wed, 27 May 2015 19:03:57 +0100 (BST) From: Pavel Fedin References: <1430921082-16779-1-git-send-email-shlomopongratz@gmail.com> <1430921082-16779-2-git-send-email-shlomopongratz@gmail.com> <20150527181202.2ef26ca6@nial.brq.redhat.com> In-reply-to: <20150527181202.2ef26ca6@nial.brq.redhat.com> Date: Wed, 27 May 2015 21:03:55 +0300 Message-id: <021a01d098a7$7fd6ac40$7f8404c0$@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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: 'Igor Mammedov' , shlomopongratz@gmail.com Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org, 'Shlomo Pongratz' Hello! > I think encoding should be CPU type specific i.e. not defined by what > GIC can support and once we add CPU type with 8 cores, it would provide > it's own version of mpidr_read since it would be defined by spec > how to encode aff0. I have redone this thing from scratch: https://lists.gnu.org/archive/html/qemu-devel/2015-05/msg04495.html My implementation does exactly this. It simply introduces CPU-specific MPIDR value which CPUs can set as they wish. Also this is used by KVM because KVM has its own ideas about how CPUs are clustered. I posted that without RFC, because i think it's ready for application, but my message seems to have been lost. Looks like i forgot Cc to the maintainer. My current vGICv3 work-in-progress is based on this. If Shlomo does not respond until friday, i think i'll post a new vGICv3 series based on master. Kind regards, Pavel Fedin Expert Engineer Samsung Electronics Research center Russia