linux-kernel - Re: [PATCH v2 0/6] consolidate and cleanup CPU capacity

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] [day] [month] [year] [list]

Message-ID: <688adbc9-6dbc-4c98-971e-630525ff003b@arm.com>
Date:   Wed, 18 Oct 2023 12:27:55 +0100
From:   Lukasz Luba <lukasz.luba@....com>
To:     Vincent Guittot <vincent.guittot@...aro.org>
Cc:     conor.dooley@...rochip.com, suagrfillet@...il.com,
        bsegall@...gle.com, dietmar.eggemann@....com, peterz@...radead.org,
        mingo@...hat.com, rafael@...nel.org, sudeep.holla@....com,
        aou@...s.berkeley.edu, palmer@...belt.com,
        paul.walmsley@...ive.com, linux-pm@...r.kernel.org,
        linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org, pierre.gondois@....com,
        ionela.voinescu@....com, viresh.kumar@...aro.org,
        bristot@...hat.com, will@...nel.org, catalin.marinas@....com,
        linux@...linux.org.uk, ajones@...tanamicro.com, lftan@...nel.org,
        gregkh@...uxfoundation.org, juri.lelli@...hat.com,
        rostedt@...dmis.org, mgorman@...e.de, vschneid@...hat.com
Subject: Re: [PATCH v2 0/6] consolidate and cleanup CPU capacity



On 10/9/23 11:36, Vincent Guittot wrote:
> This is the 1st part of consolidating how the max compute capacity is
> used in the scheduler and how we calculate the frequency for a level of
> utilization.
> 
> Fix some unconsistancy when computing frequency for an utilization. There
> can be a mismatch between energy model and schedutil.
> 
> Next step will be to make a difference between the original
> max compute capacity of a CPU and what is currently available when
> there is a capping applying forever (i.e. seconds or more).
> 
> 

I have tested the patches apart from the last CPPC because the platform
didn't have that. The EAS is working OK, so feel free to add:

Tested-by: Lukasz Luba <lukasz.luba@....com>

apart from the patch 6/6 - with the cppc changes

Regards,
Lukasz