From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56594) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ysv2Y-0002IQ-M2 for qemu-devel@nongnu.org; Thu, 14 May 2015 11:27:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ysv2T-0001DH-Np for qemu-devel@nongnu.org; Thu, 14 May 2015 11:27:14 -0400 Received: from mailout3.w1.samsung.com ([210.118.77.13]:55071) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ysv2T-0001BX-H9 for qemu-devel@nongnu.org; Thu, 14 May 2015 11:27:09 -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 <0NOC00IIIIX3AO20@mailout3.w1.samsung.com> for qemu-devel@nongnu.org; Thu, 14 May 2015 16:27:03 +0100 (BST) From: Pavel Fedin References: <00c901d08990$2763c410$762b4c30$@samsung.com> <034301d08c92$dccf6e80$966e4b80$@samsung.com> <03e001d08caf$d7fcd1a0$87f674e0$@samsung.com> <006901d08d84$ba7f0370$2f7d0a50$@samsung.com> In-reply-to: Date: Thu, 14 May 2015 18:27:02 +0300 Message-id: <004401d08e5a$6dcee1e0$496ca5a0$@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 v2] Add virt-v3 machine that uses GIC-500 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: 'Shlomo Pongratz' , qemu-devel@nongnu.org Cc: 'Peter Maydell' , 'Claudio Fontana' , 'Shannon Zhao' , christoffer.dall@linaro.org Hello! > I wonder how it works for you. Do you aware of an alternative way to configure the clock > irqflags for more then 24 cores, or is it just ignored. Unfortunately i don't know how it works. > My current status is as follows: > With 64 cores there is no printouts what so ever. > With 32 cores the boot usually get stuck after the message "[ 45.719102] SCSI subsystem > initialized" > With 24 cores the system noontimes complete the boot and sometimes get stuck like the 32 > cores system. I will recheck later when i get back to qemu. I will pull the latest HEAD and fix IRQ affinity specification. But, i think that most likely you'll have to debug this yourself. Because i suggest it will work. :) >> Yes, i just left it as it was because it already works fine with ARM64. Actually, >> TYPE_AARCH64_CPU is a subclass of TYPE_ARM_CPU. > > I see but I guess that I want aarch64_cpu_initfn to be called and not arm_cpu_initfn. I guess that the correct class will be returned. Otherwise it would not work at all. You can check this if you want to. >> BTW, just for interest, have you tried to do anything with KVM support of vGICv3? I have >> some code but it's inherently unstable and lock up for unknown (yet) reason. > > No, this is because I don't have an ARM64 based server needed for running KVM for ARM64. Ok. Then it looks like i'm going to be the first to do this. I hope you'll complete the integration soon because vGICv3 has to be based upon your work. Kind regards, Pavel Fedin Expert Engineer Samsung Electronics Research center Russia