Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754629AbbKXOwT (ORCPT ); Tue, 24 Nov 2015 09:52:19 -0500 Received: from mail.dev.rtsoft.ru ([213.79.90.226]:41646 "EHLO dev.rtsoft.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754001AbbKXOwR (ORCPT ); Tue, 24 Nov 2015 09:52:17 -0500 Message-ID: <5654799E.5080903@dev.rtsoft.ru> Date: Tue, 24 Nov 2015 17:52:14 +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: Vladimir Murzin , kuznetsovg@dev.rtsoft.ru, Ian Campbell , Mason , Ard Biesheuvel , 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> In-Reply-To: <20151123130424.GQ8644@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: 1823 Lines: 48 >> Just booted mainline... unline linux-imx, it does not try to init cpu1. >> >> However, imx6dl.dtsi from mainline also has both cpu@0 and cpu@1 >> >> So missing piece in linux-imx is elsewhere :( > > It works as you mentioned - and it relies upon the code you tried to > modify. > > The early boot code detects that the boot CPU is not SMP capable, so > through SMP_ON_UP, it "turns off" SMP support by fixing up the code > and making is_smp() return false. > > This prevents smp_init_cpus() being called, which in turn prevents > imx_smp_init_cpus() executing, which prevents the CPU possible mask > including any CPU but the boot CPU. > > As only the boot CPU is possible, this prevents the SMP code trying > to bring any secondary CPUs online. I'm still trying to understand what is going on, and my printk()s show that this is not entirely true. When smp_init() is entered on mainline om imx6s, cpu_possible_mask and cpu_present_mask both contain two cpus. These get initialized in arm_dt_init_cpu_maps() and stay unmodified since then. But cpu_online() returns 1 for cpu0 and 0 from cpu1 - thus it is cpu_online() check, not possible_mask or present_mask, that prevents cpu1 initialization attempt. 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. This does not seem to be intended difference. -- 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/