Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S967836Ab3DRRBc (ORCPT ); Thu, 18 Apr 2013 13:01:32 -0400 Received: from smtp02.citrix.com ([66.165.176.63]:24142 "EHLO SMTP02.CITRIX.COM" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S967741Ab3DRRB2 (ORCPT ); Thu, 18 Apr 2013 13:01:28 -0400 X-IronPort-AV: E=Sophos;i="4.87,503,1363132800"; d="scan'208";a="19288438" Date: Thu, 18 Apr 2013 18:01:14 +0100 From: Stefano Stabellini X-X-Sender: sstabellini@kaball.uk.xensource.com To: Nicolas Pitre CC: Stefano Stabellini , Russell King - ARM Linux , "xen-devel@lists.xensource.com" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "will.deacon@arm.com" , "arnd@arndb.de" , "rob.herring@calxeda.com" , "marc.zyngier@arm.com" Subject: Re: [PATCH v6 1/4] arm: introduce psci_smp_ops In-Reply-To: Message-ID: References: <1365167495-18508-1-git-send-email-stefano.stabellini@eu.citrix.com> <20130418161341.GB14496@n2100.arm.linux.org.uk> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1533 Lines: 33 On Thu, 18 Apr 2013, Nicolas Pitre wrote: > On Thu, 18 Apr 2013, Stefano Stabellini wrote: > > > On Thu, 18 Apr 2013, Russell King - ARM Linux wrote: > > > This should allow the Xen problem to be resolved, because Xen will > > > provide the PSCI operations, and it's correct in that case to override > > > the platform's SMP operations. > > > > Yes, increasing the priority of PSCI helps Xen a lot. > > In order to completely solve the issue for Xen though, another patch is > > needed (http://marc.info/?l=linux-kernel&m=136630106201968&w=2) because > > of the introduction of smp_init. > > Please look at the latest smp_init patch version I sent to you. It > shouldn't conflict with Xen any longer. It now returns a bool result > depending on whether it did set up smp_ops or not. CPUs are virtualized by Xen and do not reflect or expose the underlying SMP hardware and firmware features, so an hardware specific smp_init cannot run. So the smp_init patch still breaks Xen because even if smp_init can fail graciously, executing a platform specific smp_init function that tries to access registers and memory regions that are not present is going to cause an undefined behaviour. Under Xen, smp_init won't have a chance to return any value because it is going to crash first. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/