From: Bjorn Andersson <andersson@kernel.org>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: dmitry.baryshkov@linaro.org, agross@kernel.org,
konrad.dybcio@linaro.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, danny@kdrag0n.dev
Subject: Re: [PATCH] arm64: dts: qcom: sdm845: correct dynamic power coefficients
Date: Fri, 6 Jan 2023 12:28:49 -0600 [thread overview]
Message-ID: <20230106182849.kr47mdgokd4qa6zw@builder.lan> (raw)
In-Reply-To: <20230106164618.1845281-1-vincent.guittot@linaro.org>
On Fri, Jan 06, 2023 at 05:46:18PM +0100, Vincent Guittot wrote:
Seems like using get_maintainer.pl would have saved you some trouble ;)
> While stressing EAS on my dragonboard RB3, I have noticed that LITTLE cores
> where never selected as the most energy efficient CPU whatever the
> utilization level of waking task.
>
> energy model framework uses its cost field to estimate the energy with
> the formula:
>
> nrg = cost of the selected OPP * utilization / CPU's max capacity
>
> which ends up selecting the CPU with lowest cost / max capacity ration
> as long as the utilization fits in the OPP's capacity.
>
> If we compare the cost of a little OPP with similar capacity of a big OPP
> like :
> OPP(kHz) OPP capacity cost max capacity cost/max capacity
> LITTLE 1766400 407 351114 407 863
> big 1056000 408 520267 1024 508
>
> This can be interpreted as the LITTLE core consumes 70% more than big core
> for the same compute capacity.
>
> According to [1], LITTLE consumes 10% less than big core for Coremark
> benchmark at those OPPs. If we consider that everything else stays
> unchanged, the dynamic-power-coefficient of LITTLE core should be
> only 53% of the current value: 290 * 53% = 154
>
> Set the dynamic-power-coefficient of CPU0-3 to 154 to fix the energy model.
>
This is sounds reasonable.
But if the math was wrong for SDM845, I would assume that sm8150 and
sm8250 are wrong as well, as that's what 0e0a8e35d725 is based on. And
should I assume that patches for other platforms are off by 53% as well?
Can you help me understand how to arrive at this number? (Without
considering everything else stays unchanged, if needed).
Regards,
Bjorn
> [1] https://github.com/kdrag0n/freqbench/tree/master/results/sdm845/main
>
> Fixes: 0e0a8e35d725 ("arm64: dts: qcom: sdm845: correct dynamic power coefficients")
> Signed-off-by: Vincent Guittot <vincent.guittot@linaro.org>
> ---
> arch/arm64/boot/dts/qcom/sdm845.dtsi | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi b/arch/arm64/boot/dts/qcom/sdm845.dtsi
> index 65032b94b46d..869bdb9bce6e 100644
> --- a/arch/arm64/boot/dts/qcom/sdm845.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sdm845.dtsi
> @@ -198,7 +198,7 @@ CPU0: cpu@0 {
> reg = <0x0 0x0>;
> enable-method = "psci";
> capacity-dmips-mhz = <611>;
> - dynamic-power-coefficient = <290>;
> + dynamic-power-coefficient = <154>;
> qcom,freq-domain = <&cpufreq_hw 0>;
> operating-points-v2 = <&cpu0_opp_table>;
> interconnects = <&gladiator_noc MASTER_APPSS_PROC 3 &mem_noc SLAVE_EBI1 3>,
> @@ -222,7 +222,7 @@ CPU1: cpu@100 {
> reg = <0x0 0x100>;
> enable-method = "psci";
> capacity-dmips-mhz = <611>;
> - dynamic-power-coefficient = <290>;
> + dynamic-power-coefficient = <154>;
> qcom,freq-domain = <&cpufreq_hw 0>;
> operating-points-v2 = <&cpu0_opp_table>;
> interconnects = <&gladiator_noc MASTER_APPSS_PROC 3 &mem_noc SLAVE_EBI1 3>,
> @@ -243,7 +243,7 @@ CPU2: cpu@200 {
> reg = <0x0 0x200>;
> enable-method = "psci";
> capacity-dmips-mhz = <611>;
> - dynamic-power-coefficient = <290>;
> + dynamic-power-coefficient = <154>;
> qcom,freq-domain = <&cpufreq_hw 0>;
> operating-points-v2 = <&cpu0_opp_table>;
> interconnects = <&gladiator_noc MASTER_APPSS_PROC 3 &mem_noc SLAVE_EBI1 3>,
> @@ -264,7 +264,7 @@ CPU3: cpu@300 {
> reg = <0x0 0x300>;
> enable-method = "psci";
> capacity-dmips-mhz = <611>;
> - dynamic-power-coefficient = <290>;
> + dynamic-power-coefficient = <154>;
> qcom,freq-domain = <&cpufreq_hw 0>;
> operating-points-v2 = <&cpu0_opp_table>;
> interconnects = <&gladiator_noc MASTER_APPSS_PROC 3 &mem_noc SLAVE_EBI1 3>,
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-01-06 18:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 16:46 [PATCH] arm64: dts: qcom: sdm845: correct dynamic power coefficients Vincent Guittot
2023-01-06 18:28 ` Bjorn Andersson [this message]
2023-01-09 17:02 ` Vincent Guittot
2023-01-18 23:26 ` Bjorn Andersson
2023-02-27 9:11 ` Vincent Guittot
2023-03-16 3:21 ` Bjorn Andersson
-- strict thread matches above, loose matches on Subject: below --
2023-01-06 16:45 Vincent Guittot
2023-01-06 16:43 Vincent Guittot
2022-03-15 14:11 Dmitry Baryshkov
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=20230106182849.kr47mdgokd4qa6zw@builder.lan \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=danny@kdrag0n.dev \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=vincent.guittot@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