Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S967640Ab3DRQkK (ORCPT ); Thu, 18 Apr 2013 12:40:10 -0400 Received: from mail-qe0-f43.google.com ([209.85.128.43]:45106 "EHLO mail-qe0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S936231Ab3DRQkI (ORCPT ); Thu, 18 Apr 2013 12:40:08 -0400 Date: Thu, 18 Apr 2013 12:40:05 -0400 (EDT) From: Nicolas Pitre To: Stefano Stabellini cc: 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.03 (LFD 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: 973 Lines: 23 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. Nicolas -- 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/