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: <9382ea70-cc50-7b78-f5de-716678bdefbf@arm.com>
Date:   Wed, 4 Nov 2020 10:58:43 +0000
From:   Lukasz Luba <lukasz.luba@....com>
To:     rafael@...nel.org
Cc:     linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
        linux-doc@...r.kernel.org, devicetree@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org, robh+dt@...nel.org,
        amitk@...nel.org, corbet@....net, daniel.lezcano@...aro.org,
        Dietmar.Eggemann@....com, morten.rasmussen@....com,
        qperret@...gle.com, dianders@...omium.org, mka@...omium.org,
        rnayak@...eaurora.org, sudeep.holla@....com,
        viresh.kumar@...aro.org, sboyd@...nel.org, nm@...com
Subject: Re: [PATCH v4 0/4] Clarify abstract scale usage for power values in
 Energy Model, EAS and IPA

Hi Rafael,

On 11/3/20 9:05 AM, Lukasz Luba wrote:
> Hi all,
> 
> The Energy Model supports power values expressed in an abstract scale.
> This has an impact on Intelligent Power Allocation (IPA) and should be
> documented properly. Kernel sub-systems like EAS, IPA and DTPM
> (new comming PowerCap framework) would use the new flag to capture
> potential miss-configuration where the devices have registered different
> power scales, thus cannot operate together.
> 
> There was a discussion below v2 of this patch series, which might help
> you to get context of these changes [2].
> 
> The agreed approach is to have the DT as a source of power values expressed
> always in milli-Watts and the only way to submit with abstract scale values
> is via the em_dev_register_perf_domain() API.
> 
> Changes:
> v4:
> - change bool to int type for 'miliwatts' in struct em_perf_domain
>    (suggested by Quentin)
> - removed one sentence from patch 2/4 in IPA doc power_allocator.rst
>    (suggested by Quentin)
> - added reviewed-by from Quentin to 1/4, 3/4, 4/4 patches

There was no major objections in the v3 and this v4 just addressed
minor comments. The important discussions mostly happen in v2.

Could you take the patches via your tree, please?

Regards,
Lukasz

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ