linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Lukasz Luba <lukasz.luba@arm.com>
Cc: Vincent Guittot <vincent.guittot@linaro.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	linux-kernel@vger.kernel.org, rafael@kernel.org,
	linux-pm@vger.kernel.org, Dietmar.Eggemann@arm.com,
	"daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>
Subject: Re: [PATCH 2/2] cpufreq: Update CPU capacity reduction in store_scaling_max_freq()
Date: Tue, 11 Oct 2022 10:38:04 +0200	[thread overview]
Message-ID: <Y0UrbBioezoyeez/@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <7ded9241-6c21-6631-8910-9f1150db6724@arm.com>

On Mon, Oct 10, 2022 at 11:46:29AM +0100, Lukasz Luba wrote:
> 
> +CC Daniel, since I have mentioned a few times DTPM
> 
> On 10/10/22 11:25, Peter Zijlstra wrote:
> > On Mon, Oct 10, 2022 at 11:12:06AM +0100, Lukasz Luba wrote:
> > > BTW, those Android user space max freq requests are not that long,
> > > mostly due to camera capturing (you can see a few in this file,
> > > e.g. [1]).
> > 
> > It does what now ?!? Why is Android using this *at*all* ?
> 
> It tries to balance the power budget, before bad things happen
> randomly (throttling different devices w/o a good context what's
> going on). Please keep in mind that we have ~3 Watts total power
> budget in a phone, while several devices might be suddenly used:
> 1. big CPU with max power ~3-3.5 Watts (and we have 2 cores on pixel6)
> 2. GPU with max power ~6Watts (normally ~1-2Watts when lightly used)
> 3. ISP (Image Signal Processor) up to ~2Watts
> 4. DSP also up to 1-2Watts
> 
> We don't have currently a good mechanism which could be aware
> of the total power/thermal budget and relations between those
> devices. Vendors and OEMs run experiments on devices and profile
> them to work more predictable in those 'important to users' scenarios.
> 
> AFAIK Daniel Lescano is trying to help with this new interface
> for PowerCap: DTMP. It might be use as a new interface for those known
> scenarios like the camera snapshot. But that interface is on the list
> that I have also mentioned - it's missing the notification mechanism
> for the scheduler reduced capacity due to user-space new scenario.

DTMP is like IPA but including random devices? Because I thought IPA
already did lots of this.

  reply	other threads:[~2022-10-11  8:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30  9:48 [PATCH 1/2] cpufreq: Change macro for store scaling min/max frequency Lukasz Luba
2022-09-30  9:48 ` [PATCH 2/2] cpufreq: Update CPU capacity reduction in store_scaling_max_freq() Lukasz Luba
2022-10-10  5:39   ` Viresh Kumar
2022-10-10  9:02     ` Lukasz Luba
2022-10-10  9:15       ` Vincent Guittot
2022-10-10  9:30         ` Lukasz Luba
2022-10-10  9:32           ` Vincent Guittot
2022-10-10 10:12             ` Lukasz Luba
2022-10-10 10:22               ` Vincent Guittot
2022-10-10 10:49                 ` Lukasz Luba
2022-10-10 12:21                   ` Vincent Guittot
2022-10-10 13:05                     ` Lukasz Luba
2022-10-10 10:25               ` Peter Zijlstra
2022-10-10 10:46                 ` Lukasz Luba
2022-10-11  8:38                   ` Peter Zijlstra [this message]
2022-10-11 10:25                     ` Lukasz Luba
2022-10-10  5:36 ` [PATCH 1/2] cpufreq: Change macro for store scaling min/max frequency Viresh Kumar
2022-10-10  8:49   ` Lukasz Luba

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=Y0UrbBioezoyeez/@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=Dietmar.Eggemann@arm.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=rafael@kernel.org \
    --cc=vincent.guittot@linaro.org \
    --cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).