From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marc Zyngier Subject: Re: [Android-virt] [PATCH v5 11/13] ARM: KVM: Support SMP hosts Date: Mon, 19 Dec 2011 15:19:11 +0000 Message-ID: <4EEF55EF.9050309@arm.com> References: <20111211102403.21693.6887.stgit@localhost> <20111211102529.21693.62306.stgit@localhost> <4EEED68D.5040307@virtualopensystems.com> Mime-Version: 1.0 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: 8BIT Cc: android-virt@lists.cs.columbia.edu, a.motakis@virtualopensystems.com, "tech@virtualopensystems.com" , "avi@redhat.com" , "kvm@vger.kernel.org" To: Christoffer Dall Return-path: Received: from service87.mimecast.com ([91.220.42.44]:33635 "EHLO service87.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750880Ab1LSPTM convert rfc822-to-8bit (ORCPT ); Mon, 19 Dec 2011 10:19:12 -0500 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 19/12/11 14:57, Christoffer Dall wrote: > On Mon, Dec 19, 2011 at 1:15 AM, Antonios Motakis > wrote: >> On 12/11/2011 11:25 AM, Christoffer Dall wrote: >>> WARNING: This code is in development and guests do not fully boot on SMP >>> hosts yet. >> Hello, >> >> What would still be needed to fully booted SMP? For example, are there >> identified critical sections and structures that need to be worked on, >> or there are parts that still need to be reviewed to find those? Or is >> it only a matter of fixing up any existing locking/syncing introduced in >> this patch? >> > > You should simply start booting a UP guest on an SMP host, see where > it crashes and start tracking it down. For the time being, I've yet to see UP guest crashing on SMP host. On the model, that is... > Same procedure for guest SMP. That's a very different kettle of fish. I see both CPUs starting to run, and end up with both in WFI after a while, without any interrupt pending... I'll investigate that as soon as I can. M. -- Jazz is not dead. It just smells funny...