From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38968) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YzJIu-0002mY-19 for qemu-devel@nongnu.org; Mon, 01 Jun 2015 02:34:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YzJIp-000239-2d for qemu-devel@nongnu.org; Mon, 01 Jun 2015 02:34:31 -0400 Received: from mailout4.w1.samsung.com ([210.118.77.14]:62435) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YzJIo-00022P-TV for qemu-devel@nongnu.org; Mon, 01 Jun 2015 02:34:27 -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 <0NP9007SD69AAS60@mailout4.w1.samsung.com> for qemu-devel@nongnu.org; Mon, 01 Jun 2015 07:34:22 +0100 (BST) From: Pavel Fedin References: <011801d0947a$a9e1e8a0$fda5b9e0$@samsung.com> <00f701d099db$0510a990$0f31fcb0$@samsung.com> In-reply-to: Date: Mon, 01 Jun 2015 09:34:21 +0300 Message-id: <00d701d09c34$feca07f0$fc5e17d0$@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: 'Shlomo Pongratz' , qemu-devel@nongnu.org Cc: peter.maydell@linaro.org, 'Ashok Kumar' Hi! > I think we should take Igor's comment into account. The CPUS_PER_CLUSTER should not be a > constant, and maybe should be initialized in arm_cpu_initfn and aarch64_{a53|a57}_initfn, as > psci need to know it. Yes, of course. Just replace a #define with something like: int cpus_per_cluster = 8; and you're done with this. This provides good backwards compatibility as well as possibility to change this on a per-machine basis. > I understand that you suggest that I'll not use my 1 & 4 patches. I have no problem with that, > but how do I commit? Should I write that the patch series is pending until your patch series is > integrated? Just make it a part of your V3. I'm perfectly OK with that. Looks like maintainers don't want to integrate it alone. > I intend to release the V3 version during this week. Good. Kind regards, Pavel Fedin Expert Engineer Samsung Electronics Research center Russia