Linux-ARM-Kernel Archive on
 help / color / Atom feed
From: Viresh Kumar <>
To: Linus Walleij <>
Cc: Arnd Bergmann <>,
	"Rafael J . Wysocki" <>,
	SoC Team <>, arm-soc <>,
	Linux ARM <>
Subject: Re: [PATCH] ARM: config: multi_v7 Use schedutil cpufreq
Date: Fri, 27 Mar 2020 10:37:27 +0530
Message-ID: <20200327050727.yxzu4b5mu2rdkdz4@vireshk-i7> (raw)
In-Reply-To: <>

On 26-03-20, 23:08, Linus Walleij wrote:
> On Wed, Mar 25, 2020 at 5:28 PM Arnd Bergmann <> wrote:
> > On Mon, Mar 2, 2020 at 5:22 AM Viresh Kumar <> wrote:
> > > FWIW, I have tried something similar for arm64 earlier.
> > >
> > >
> >
> > I've dropped this one and not applied it for now after rereading the old thread.
> > If there is a broader agreement on what the default should be, please
> > collect more Acks and we can apply whatever you come up with.
> I think there is a more compelling argument: if I understand correctly
> the energy aware scheduling and HMP on big.LITTLE only works
> correctly if schedutil is used as cpufreq governor (correct Vincent, Viresh?)
> That would make the default multi_v7 unusable (or misbehaving)
> on e.g. Vexpress TC2.
> Thus I suspect the Vexpress and other machines using HMP
> and big.LITTLE should just select
> That will of course make it percolate up to multi_v7 by default
> as well.
> If more magic configs are necessary to select to make a TC2
> work properly I'd like to know these as well so we can just select
> them all by default also for these targets.

I always agreed that schedutil must be selected as default governor
instead of ondemand and I still want to get my arm64 patch merged :)

And yes, schedutil will work the best for big LITTLE stuff.


linux-arm-kernel mailing list

  reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-29 21:02 Linus Walleij
2020-03-02  4:22 ` Viresh Kumar
2020-03-25 16:27   ` Arnd Bergmann
2020-03-26 22:08     ` Linus Walleij
2020-03-27  5:07       ` Viresh Kumar [this message]
2020-03-27  8:06       ` Vincent Guittot

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:

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

  git send-email \
    --in-reply-to=20200327050727.yxzu4b5mu2rdkdz4@vireshk-i7 \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-ARM-Kernel Archive on

Archives are clonable:
	git clone --mirror linux-arm-kernel/git/0.git
	git clone --mirror linux-arm-kernel/git/1.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-arm-kernel linux-arm-kernel/ \
	public-inbox-index linux-arm-kernel

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone