From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38482) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YyODk-0000TQ-BW for qemu-devel@nongnu.org; Fri, 29 May 2015 13:37:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YyODh-0005zd-5Y for qemu-devel@nongnu.org; Fri, 29 May 2015 13:37:24 -0400 Received: from mailout1.w1.samsung.com ([210.118.77.11]:16607) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YyODg-0005yb-Ve for qemu-devel@nongnu.org; Fri, 29 May 2015 13:37:21 -0400 Received: from eucpsbgm1.samsung.com (unknown [203.254.199.244]) by mailout1.w1.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTP id <0NP400EUSGY6E900@mailout1.w1.samsung.com> for qemu-devel@nongnu.org; Fri, 29 May 2015 18:37:18 +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> <01ab01d09a0a$c1bdb450$45391cf0$@samsung.com> <20150529150326.451478f4@nial.brq.redhat.com> In-reply-to: <20150529150326.451478f4@nial.brq.redhat.com> Date: Fri, 29 May 2015 20:37:13 +0300 Message-id: <024b01d09a36$1ba8c060$52fa4120$@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' Hi! > Well KVM side should be fixed instead of driving us along wrong route. I have studied the question a bit more, and i discovered that MPIDR access on ARM is not trapped by KVM. And guest would always get the same value as host would. Theoretically you could modify the kernel so that PSCI accepts IDs set by qemu, but in this case we would have inconsistency between device tree and real IDs. And there seems to be no way round. Kind regards, Pavel Fedin Expert Engineer Samsung Electronics Research center Russia