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: <057547c9-773e-4ba2-a754-aede29d07daa@ti.com>
Date: Wed, 11 Feb 2026 15:29:58 -0600
From: Kendall Willis <k-willis@...com>
To: "Kevin Hilman (TI)" <khilman@...libre.com>, "Rafael J. Wysocki"
	<rafael@...nel.org>, Ulf Hansson <ulf.hansson@...aro.org>,
	<linux-pm@...r.kernel.org>
CC: Dhruva Gole <d-gole@...com>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 3/3] pmdommain: add support system-wide resume latency
 constraints

Hi Kevin,
On 2/5/26 18:29, Kevin Hilman (TI) wrote:
> In addition to checking for CPU latency constraints when checking if
> OK to power down a domain, also check for QoS latency constraints in
> all devices of a domain and use that in determining the final latency
> constraint to use for the domain.
> 
> Since cpu_system_power_down_ok() is used for system-wide suspend, the
> per-device constratints are only relevant if the LATENCY_SYS QoS flag
> is set.
> 
> Signed-off-by: Kevin Hilman (TI) <khilman@...libre.com>
> ---

Were you planning to also check the CPU devices QoS latency constraints 
in the cpu_system_power_down_ok function? At present, this patch does 
not add that functionality so if the PM_QOS_FLAG_LATENCY_SYS is present 
for a CPU device, the QoS latency is not taken into account.

Best,
Kendall Willis <k-willis@...com>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ