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: <7hwmkt1vzk.fsf@baylibre.com>
Date: Tue, 06 Aug 2024 09:01:19 -0700
From: Kevin Hilman <khilman@...libre.com>
To: Nishanth Menon <nm@...com>
Cc: Tero Kristo <kristo@...nel.org>, Santosh Shilimkar
 <ssantosh@...nel.org>, linux-arm-kernel@...ts.infradead.org,
 linux-kernel@...r.kernel.org, Akashdeep Kaur <a-kaur@...com>, Markus
 Schneider-Pargmann <msp@...libre.com>, Vibhore Vardhan <vibhore@...com>,
 Dhruva Gole <d-gole@...com>
Subject: Re: [PATCH v3] firmware: ti_sci: add CPU latency constraint management

Nishanth Menon <nm@...com> writes:

> On 14:42-20240802, Kevin Hilman wrote:
>> During system-wide suspend, check if any of the CPUs have PM QoS
>> resume latency constraints set.  If so, set TI SCI constraint.
>> 
>> TI SCI has a single system-wide latency constraint, so use the max of
>> any of the CPU latencies as the system-wide value.
>> 
>> Note: DM firmware clears all constraints at resume time, so
>> constraints need to be checked/updated/sent at each system suspend.
>> 
>> Co-developed-by: Vibhore Vardhan <vibhore@...com>
>> Signed-off-by: Vibhore Vardhan <vibhore@...com>
>> Signed-off-by: Kevin Hilman <khilman@...libre.com>
>> Reviewed-by: Dhruva Gole <d-gole@...com>
>> Signed-off-by: Dhruva Gole <d-gole@...com>
>> ---
>> Depends on the TI SCI series where support for the constraints APIs
>> are added:
>> https://lore.kernel.org/r/20240801195422.2296347-1-msp@baylibre.com
>> 
>
> Unless there is a reason to maintain this patch separately, Could we
> add this to the mentioned series -> it is much easier to review and
> merge them in one go.

Sure, they can be combined for the next version.

Kevin

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ