Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751677AbbK1LNe (ORCPT ); Sat, 28 Nov 2015 06:13:34 -0500 Received: from mail.dev.rtsoft.ru ([213.79.90.226]:52781 "EHLO dev.rtsoft.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751087AbbK1LNc (ORCPT ); Sat, 28 Nov 2015 06:13:32 -0500 Message-ID: <56598C59.4070307@dev.rtsoft.ru> Date: Sat, 28 Nov 2015 14:13:29 +0300 From: Nikita Yushchenko Organization: RTSoft Software Development Center User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.8.0 MIME-Version: 1.0 To: Russell King - ARM Linux CC: kuznetsovg@dev.rtsoft.ru, Vladimir Murzin , Ian Campbell , Ard Biesheuvel , Mason , Will Deacon , Paul Kocialkowski , linux-kernel@vger.kernel.org, Masahiro Yamada , Pavel Machek , linux-arm-kernel@lists.infradead.org Subject: Re: [RFC/PATCH] arm: do not skip SMP init calls on SMP_ON_UP case References: <1448279946-19975-1-git-send-email-nyushchenko@dev.rtsoft.ru> <20151123120317.GN8644@n2100.arm.linux.org.uk> <5653015C.4020405@dev.rtsoft.ru> <56530769.4030403@arm.com> <5653099A.7020604@dev.rtsoft.ru> <56530AE6.2060407@dev.rtsoft.ru> <20151123130424.GQ8644@n2100.arm.linux.org.uk> <5654799E.5080903@dev.rtsoft.ru> <20151124153305.GD8644@n2100.arm.linux.org.uk> In-Reply-To: <20151124153305.GD8644@n2100.arm.linux.org.uk> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1546 Lines: 37 >> Not sure I understand logic behind this. With the current code, >> resulting cpu_possible_mask depends on CONFIG_SMP_ON_UP: >> - if it is set, cpu_possible_mask contains (0 1), as initialized in >> arm_dt_init_cpu_maps() >> - if it is not set, cpu_possible_mask contains (0), since >> imx_smp_init_cpus() removes 1 from there. > > Right, adding debug to arch/arm/kernel/setup.c, just before the > "if (is_smp())" shows: > > is_smp() 0 possible 3 present 1 online 1 > > which is totally wrong: if is_smp() is false, we should not be setting > up any possible CPUs. See a patch below to fix that. > > However, this doesn't matter much, because the code in setup.c won't > initialise the SMP operations struct ... But cpu start code is not the only place in the kernel that uses cpu_present_mask. Are you sure that running with invalid cpu_present_mask has no side effects? > Here's the patch to fix the DT code, which should not be setting > present CPUs when is_smp() is false. I see that this fixes the issue as well. But I still don't understand rationale behind all these is_smp() checks. This makes init sequence different with and without CONFIG_SMP_ON_UP. Isn't kernel intended to run ok without CONFIG_SMP_ON_UP? And if yes - then why not run the same init sequence in both cases? -- 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/