public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: b.zolnierkie@samsung.com (Bartlomiej Zolnierkiewicz)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/4] ARM: remove big.LITTLE switcher support
Date: Tue, 28 Jun 2016 10:18:17 +0200	[thread overview]
Message-ID: <8154264.t0CjdgHDuf@amdc1976> (raw)
In-Reply-To: <alpine.LFD.2.20.1606271540000.2550@knanqh.ubzr>


Hi,

On Monday, June 27, 2016 03:49:44 PM Nicolas Pitre wrote:
> On Mon, 27 Jun 2016, Bartlomiej Zolnierkiewicz wrote:
> 
> > Hi,
> > 
> > It seems that in mainline kernel big.LITTLE switcher support
> > may be usable only on ARM Versatile Express TC2 platform
> > (but even this platform doesn't enable it in its defconfig).
> 
> It is also used on some Samsung targets.

Could you please explain this more?  AFAIK mainline never
had working IKS solution (big.LITTLE switcher support +
arm_big_little CPUfreq driver support) on any Samsung SoC.

> > The following patchset removes big.LITTLE switcher support
> > (from both ARM core and arm_big_little CPUfreq driver) in
> > favor of using HMP.
> > 
> > Since HMP support at scheduler level is not yet merged this
> > patchset is probably premature and thus is marked as RFC.
> 
> It is premature indeed.
> 
> And before this is removed, comparison with power/performance benchmark 
> numbers will have to be provided as well to justify this removal.  At 
> the moment there is nothing else in mainline that can achieve what this 
> code does.

I agree given that this code has real users and according
to my research on mainline kernel it seems that the IKS
functionality (bL switcher core code together with
arm_bit_little CPUfreq driver support) is usable only on
TC2 and even this platform doesn't enable it by default.

IOW I would really like to get the confirmation that there
are platforms that are making use of IKS functionality
currently with the mainline  kernel.  Otherwise we should
either consider its removal or enable it on platforms that
are supposed to use it.

> We all agree that the scheduler based solution is the best way to do it. 
> But this has been a couple years already and this is still work in 
> progress.

Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics

  reply	other threads:[~2016-06-28  8:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-27 11:26 [RFC PATCH 0/4] ARM: remove big.LITTLE switcher support Bartlomiej Zolnierkiewicz
2016-06-27 11:26 ` [RFC PATCH 1/4] " Bartlomiej Zolnierkiewicz
2016-06-27 11:26 ` [RFC PATCH 2/4] cpufreq: arm_big_little: " Bartlomiej Zolnierkiewicz
2016-06-27 11:26 ` [RFC PATCH 3/4] cpufreq: exynos: remove big.LITTLE switcher dependency Bartlomiej Zolnierkiewicz
2016-06-27 11:26 ` [RFC PATCH 4/4] irqchip/gic: remove big.LITTLE switcher support Bartlomiej Zolnierkiewicz
2016-06-27 19:49 ` [RFC PATCH 0/4] ARM: " Nicolas Pitre
2016-06-28  8:18   ` Bartlomiej Zolnierkiewicz [this message]
2016-06-28 16:13     ` Nicolas Pitre

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=8154264.t0CjdgHDuf@amdc1976 \
    --to=b.zolnierkie@samsung.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox