From mboxrd@z Thu Jan 1 00:00:00 1970 From: khilman@linaro.org (Kevin Hilman) Date: Fri, 08 Aug 2014 11:04:02 -0700 Subject: [PATCH] ARM: multi_v7_defconfig: major refresh In-Reply-To: (Olof Johansson's message of "Fri, 1 Aug 2014 04:03:36 -0700") References: <1406052070-6207-1-git-send-email-olof@lixom.net> <53DB6B4F.9080605@arm.com> <1406890899.2794.40.camel@linaro1.home> Message-ID: <7hlhqy3lkd.fsf@paris.lan> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Olof Johansson writes: > On Fri, Aug 1, 2014 at 4:01 AM, Jon Medhurst (Tixy) wrote: >> On Fri, 2014-08-01 at 11:26 +0100, Sudeep Holla wrote: >>> >>> On 22/07/14 19:01, Olof Johansson wrote: >>> > This is a major refresh of the multi_v7_defconfig: >>> > >>> > - Bring over a bunch of Samsung drivers to make ODROID-U3 and Chromebooks usable >>> > * Enable big.LITTLE >>> > * MCPM >>> [...] >> >>> > +CONFIG_BIG_LITTLE=y >>> > +CONFIG_BL_SWITCHER=y >>> >>> IIUC, this will enable switcher code by default. I am not sure if this >>> is intentional ? E.g.: After this I can have only 2 active cpus instead >>> of 5 on my Vexpress TC2 platform. >>> >>> IMO we can keep this enabled by default in the build, but disabled >>> by default on boot. >> >> TC2 has a big.LITTLE processor and the switcher is the only mainlined >> way of making any kind of proper use of big.LITTLE, so why not have it >> enabled by default? > > +1. > I disagree. The bL switcher is a stopgap used on products (which have their own defconfigs anyways) but upstream development is focused on HMP (or whatever the current buzzword is for the kernel directly scheduling both big and little cores.) So IMO, for upstream coverage, we should *not* be enabling the switcher but should be letting the scheduler directly manage all CPUs. At least on Exynos, with MCPM support merged, the kernel can boot up all the CPUs and directly manage them. Kevin