From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37204) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YyJNR-0000sI-F7 for qemu-devel@nongnu.org; Fri, 29 May 2015 08:27:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YyJNO-0005xe-7C for qemu-devel@nongnu.org; Fri, 29 May 2015 08:27:05 -0400 Received: from mailout3.w1.samsung.com ([210.118.77.13]:60075) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YyJNO-0005xY-1T for qemu-devel@nongnu.org; Fri, 29 May 2015 08:27:02 -0400 Received: from eucpsbgm2.samsung.com (unknown [203.254.199.245]) by mailout3.w1.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTP id <0NP4002V82KYQY70@mailout3.w1.samsung.com> for qemu-devel@nongnu.org; Fri, 29 May 2015 13:26:58 +0100 (BST) From: Pavel Fedin References: <011801d0947a$a9e1e8a0$fda5b9e0$@samsung.com> <20150529103652.30d30a3d@nial.brq.redhat.com> <011d01d099ec$f4f5b7a0$dee126e0$@samsung.com> <20150529111858.4b7b0db9@nial.brq.redhat.com> In-reply-to: <20150529111858.4b7b0db9@nial.brq.redhat.com> Date: Fri, 29 May 2015 15:26:57 +0300 Message-id: <01ab01d09a0a$c1bdb450$45391cf0$@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] Use Aff1 with mpidr List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: 'Igor Mammedov' Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org, 'Ashok Kumar' , 'Shlomo Pongratz' Hello! > That's what I see as correct way to go > and along the way teach KVM to not derive mpidr encoding from vcpuid > and use QEMU provided mpidr value, that way mpidr would be consistent. Yes, and this would make modelling of real hardware working much better. However, unfortunately, i have just tested it, and it does not work. MPIDR can be set for the vCPU, and i believe it will even give back the value when read. But PSCI completely ignores this setting. > As it currently stands QEMU notion of mpidr and KVM's will diverge > onece CPU count goes above 16 CPUs. Yes, but fortunately the code which cares about it (PSCI and Shlomo's GICv3 software emulation) is not used with KVM. So i think we have no other choice if we want to be compatible with current KVM APIs. Kind regards, Pavel Fedin Expert Engineer Samsung Electronics Research center Russia