Hi ARM folks!
I have some work to do with EAS + IPA.
I have a platform with arm64 4 big + 4 LITTLE that will
hopefully get EAS and IPA (when I solve some thermal issues).
Unfortunately, in this SoC and code we don't have idle states
(new SoCs will just get normal psci support).
I run different kernel versions, also your latest integration-next
(after dropping whole /drivers/usb because the changes in that branch
broke it).
Have you ever tried to evaluate EAS on a platform which has only WFI
idle? Do you know what could be the impact on the EAS?
I have some other thought and issues to discuss regarding EAS
(migrations, load balancing, etc) but this question regarding idle is
probably fundamental.
Cheers,
Lukasz Luba
Hi all,
The 'experimental/eas-dev' branch (which holds the candidate EAS patches
for the next Android Kernel version) has been updated to Linux 4.18:
https://android.googlesource.com/kernel/common exprimental/eas-dev
All the EAS patches are also available as part of the Android stack
maintained by Amit Pundir in the 'android-mainline-tracking' branch
available on AOSP.
If you wish to contribute patches to EAS that you think are
Android-specific, please do so by posting them to AOSP Gerrit against
the 'experimental/eas-dev' branch.
The branch will be rebased and force-pushed at each kernel release
(e.g. 4.18, 4.19), hence maintaining a clean stack of patches that will
be used during the creation of the next Android Common Kernel.
For more details about the contribution process to EAS, please refer to
the Arm developer website [1].
Cheers,
Quentin
[1] https://developer.arm.com/open-source/energy-aware-scheduling/contributing-…
Hi,
First of all: thanks for all the valuable input! @(Russell, Dietmar & Steven)
On 07/23/2018 08:51 AM, Steven Miao wrote:
> Hi Oliver,
>
> Generally these dynamic co-efficiency and static leakage power comes
> from hardware design team by running power estimation tool, however
> you can tun these co-efficiency and parameters for better performance.
>
> How did you get A7 or A15 power? Get Soc power or there's separate
> sensor for A7/A15?
Yes indeed, there are 2 seperate sensors for the A7 and A15.
> If you want to create cpu busy power model manually, you can:
> 1 leave 1 A7 + 1 A15 core online, keep other cores offline, disable
> thermal zone, disable idle state for all cores
> 2 set A7 frequency to 200Mhz, move all the task to A15, run cpu
> intensive task on A7(dhrystone, sysbench cpu test), read sensor to get
> 1 A7 power P1(read from A7 cluster sensor)
> 3 online 2 A7 core, run dhrystone on each core, and get power P2
>
> we can get 1 A7 core power@200Mhz ~= P2 - P1 (A7 power X 2 + static
> power - A7 power X 1 - static power
I followed your manual steps (using a busy loop for 10s, instead of a benchmark) and corrected my calculations (with the static
power in mind):
A7:
freq(MHz) voltage(mV) Power(mW) A7_Power(mW) Stat_Power(mW) DPC
200 918.750 34.768 12.203 10.362 72.283955
400 920.000 60.805 21.25 18.305 62.765831
600 968.750 98.046 35.084 27.878 62.306652
800 1042.500 148.095 52.285 43.525 60.136063
1000 1116.250 212.214 76.112 59.99 61.084382
1200 1190.000 288.958 99.993 88.972 58.842948
1400 1288.750 411.936 144.807 122.322 62.276495
mean: 62
A15:
freq(MHz) voltage(mV) Power(mW) A15_Power(mW) Stat_Power(mW) DPC
200 916250 122.584 31.139 60.306 185.458477
500 916250 225.101 68.774 87.553 163.842401
800 942500 349.158 112.432 124.294 158.211202
1100 1016250 540.78 169.556 201.668 149.251725
1400 1078750 779.19 258.214 262.762 158.493016
1700 1180000 1179.344 392.107 395.13 165.650083
2000 1320000 1969.764 648.768 672.228 186.170798
mean: 164
The ratio between A15 and A7 is now 164/62 = 2.645
I hope the dynamic-power-coefficient's are more accurate now?
> dynamic-power-coefficient ~= 400 - 500 is reasonable for big core
> dynamic-power-coefficient ~= 100 is reasonable for LITTLE core.
> For IPA it can work effectively with a poor power model(not so
> accurate), for EAS it just need power model of LITTLE core and big
> core is proportional.
I'm guessing my values differ from your suggested values, because it's 32bit ARM?
Best regards,
Oliver
Good day, dear sir.
My name is Sevgi.
I am a woman, who believe in a destiny with a cheerful future for myself and that you could become a part of it.
I do want to be next to a loving man. I wish to find a man that can give me a real hope and love!
Hope you're interested in becoming a part of my adventure and will reply back soon!
If you are interested in getting to know me closer, please write to my personal e-mail - beautysevgi(a)fastmail.com
Your true soul,
Sevgi.
Hello everyone,
I hope this is the right place to ask, otherwise please just point me in the right direction.
I'm currently testing the EAS patches [v4] on an ODROID-XU3 board, which has an Exynos5422 SoC. However, the corresponding DT is missing the "dynamic-power-coefficient" that is needed for an appropriate EM.
So I'm trying to compute the dynamic-power-coefficient according to the formula:
Pdyn = dynamic-power-coefficient * V^2 * f
The frequency f is given by the DT.The actual Voltage and Power are determined by means of the on-chip sensors (returns the values for the specific cluster). When using the Voltage given in the DT, the differences for the d-p-coefficient are negligible.
So I'm calculating the d-p-coefficient (mW/MHz/uV^2) by reading out the following SoC sensor values.
For the little cluster (A7):
frequency(MHz) Voltage(V) Power(mW) Dynamic-power-coefficient
200 0.9175 49.470 ~2.938*10^-13
400 0.9165 91.892 ~2.736*10^-13
600 0.9638 149.454 ~2.682*10^-13
800 1.0263 223.453 ~2.652*10^-13
1000 1.1000 327.707 ~2.708*10^-13
1200 1.1725 445.899 ~2.703*10^-13
1400 1.2713 627.010 ~2.771*10^-13
For the big cluster (A15):
frequency(MHz) Voltage(V) Power(mW) Dynamic-power-coefficient
200 0.9162 159.676 ~9.510*10^-13
500 0.9138 325.480 ~7.797*10^-13
800 0.9288 511.360 ~7.410*10^-13
1100 1.0063 828.020 ~7.434*10^-13
1400 1.0713 1209.774 ~7.530*10^-13
1700 1.1750 1835.784 ~7.822*10^-13
2000 1.2700 2661.849 ~8.252*10^-13
But those values are way off for the DT, unless I multiply the d-p-coefficient with 10^15.
Assuming the Power value needs to be subtracted by a static component (power usage when idle), the results change as follows:
For the little cluster (A7):
frequency(MHz) Voltage(V) P-dyn(mW) Dynamic-power-coefficient
200 0.9175 36,381 ~2,160*10^-13
400 0.9165 73,438 ~2,186*10^-13
600 0.9638 122,470 ~2,197*10^-13
800 1.0263 184,135 ~2,185*10^-13
1000 1.1000 270,425 ~2,234*10^-13
1200 1.1725 367,121 ~2,225*10^-13
1400 1.2713 513,989 ~2,271*10^-13
For the big cluster (A15):
frequency(MHz) Voltage(V) P-dyn(mW) Dynamic-power-coefficient
200 0.9162 99,834 ~5,945*10^-13
500 0.9138 244,651 ~5,860*10^-13
800 0.9288 401,986 ~5,825*10^-13
1100 1.0063 664,565 ~5,966*10^-13
1400 1.0713 985,268 ~6,132*10^-13
1700 1.1750 1494,173 ~6,366*10^-13
2000 1.2700 2086,273 ~6,467*10^-13
While looking for examples in the kernel that calculate the dynamic-power-coefficient, I found this patch [1] by Caesar Wang that introduced this value for the rk3399 big cluster.
Unfortunately, I'm unable to reproduce the same results for the coefficient with the given values. My results are also with a 10^-13 factor and even when I scale them with 10^15, my results have a certain margin of error:
> frequency(MHz) Voltage(V) Current(mA) Dynamic-power-coefficient (My) d-p-coefficient
> 24 0.8 15
> 48 0.8 23 ~417 ~598
> 96 0.8 40 ~443 ~520
> 216 0.8 82 ~438 ~474
> 312 0.8 115 ~430 ~460
> 408 0.8 150 ~455 ~459
Is this the right approach, or am I missing something?
Hope someone can help me out.
Thanks in advance,
Oliver Effland
[1] https://patchwork.kernel.org/patch/9861505/