lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49306168-c0bb-4d22-affe-6129ab35ffd8@arm.com>
Date: Tue, 19 Dec 2023 11:33:58 +0000
From: Lukasz Luba <lukasz.luba@....com>
To: Dietmar Eggemann <dietmar.eggemann@....com>
Cc: rui.zhang@...el.com, amit.kucheria@...durent.com,
 linux-kernel@...r.kernel.org, amit.kachhap@...il.com,
 daniel.lezcano@...aro.org, viresh.kumar@...aro.org, len.brown@...el.com,
 pavel@....cz, mhiramat@...nel.org, qyousef@...alina.io, wvw@...gle.com,
 linux-pm@...r.kernel.org, rafael@...nel.org
Subject: Re: [PATCH v5 08/23] PM: EM: Introduce runtime modifiable table



On 12/12/23 18:50, Dietmar Eggemann wrote:
> On 29/11/2023 12:08, Lukasz Luba wrote:
>> The new runtime table can be populated with a new power data to better
>> reflect the actual efficiency of the device e.g. CPU. The power can vary
>> over time e.g. due to the SoC temperature change. Higher temperature can
>> increase power values. For longer running scenarios, such as game or
>> camera, when also other devices are used (e.g. GPU, ISP) the CPU power can
> 
> Don't understand this sentence. So CPU power changes with higher
> temperature and for longer running scenarios when other devices are
> involved? Not getting the 2. part.

Total power consists of:
1. dynamic power - related to the freq, voltage^2 and logic capacitance
    size involved in switching during the computation
2. static power - aka. leakage - depends on voltage and
    temperature of the silicon. The higher the temperature, the higher
    the static power.

When you heat up the SoC using e.g. GPU, you start seeing on our CPU
power plot in time a raising function. Even if your CPU was running
constantly the same workload and data for long time, this effect
will happen after you add the heat from GPU in the same chip die.

IMO this is not the right place to educate people about physics of
the chip... Some understating and higher level education would
be needed otherwise even the best patch header description won't help.
So, I would keep those patch descriptions simple.

Beside, I have explained that in a few LPC and OSPM conferences.
In the cover letter there are links to them.

> 
>> change. The new EM framework is able to addresses this issue and change
>> the EM data at runtime safely.
> 
> Maybe better:
> The new EM framework addresses this issue by allowing to change the EM
> data at runtime.
> 

Sounds good, I can change that.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ