All of lore.kernel.org
 help / color / mirror / Atom feed
From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: multi_v7_defconfig: major refresh
Date: Fri, 08 Aug 2014 11:04:02 -0700	[thread overview]
Message-ID: <7hlhqy3lkd.fsf@paris.lan> (raw)
In-Reply-To: <CAOesGMi0RUbz4BSnmR92dEk3fWgN=hnENSdi55VeCXdcHLRLJQ@mail.gmail.com> (Olof Johansson's message of "Fri, 1 Aug 2014 04:03:36 -0700")

Olof Johansson <olof@lixom.net> writes:

> On Fri, Aug 1, 2014 at 4:01 AM, Jon Medhurst (Tixy) <tixy@linaro.org> 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

  parent reply	other threads:[~2014-08-08 18:04 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22 18:01 [PATCH] ARM: multi_v7_defconfig: major refresh Olof Johansson
2014-07-22 18:36 ` Arnd Bergmann
2014-07-22 20:28   ` Olof Johansson
2014-07-31  6:07     ` Tushar Behera
2014-07-31  6:26       ` Sachin Kamat
2014-08-01  6:44         ` Sachin Kamat
2014-08-01 12:53           ` Bartlomiej Zolnierkiewicz
2014-08-03  3:17             ` Olof Johansson
2014-08-05 11:39           ` Sachin Kamat
2014-08-11  3:05     ` Olof Johansson
2014-08-27  7:59       ` Bartlomiej Zolnierkiewicz
2014-11-14 11:07         ` Bartlomiej Zolnierkiewicz
2014-07-23 14:24 ` Pawel Moll
2014-08-01 10:26 ` Sudeep Holla
2014-08-01 11:01   ` Jon Medhurst (Tixy)
2014-08-01 11:03     ` Olof Johansson
2014-08-01 11:12       ` Sudeep Holla
2014-08-01 11:28         ` Jon Medhurst (Tixy)
2014-08-01 14:57           ` Sudeep Holla
2014-08-01 15:53             ` Jon Medhurst (Tixy)
2014-08-03  3:20               ` Olof Johansson
2014-08-08 18:12                 ` Kevin Hilman
2014-08-08 18:26                   ` Nicolas Pitre
2014-08-08 18:44                     ` Kevin Hilman
2014-08-08 18:37                   ` Amit Kucheria
2014-08-08 18:04       ` Kevin Hilman [this message]
2014-08-08 18:17         ` Nicolas Pitre
2014-08-01 11:06     ` Pawel Moll
2014-08-03  3:23       ` Olof Johansson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7hlhqy3lkd.fsf@paris.lan \
    --to=khilman@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.