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: <CAJZ5v0jY1HRqDtCBkDWD6FyWNGS+U1K2Y=9BqS7rgVZYS06dMg@mail.gmail.com>
Date: Mon, 16 Jun 2025 14:05:59 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: "Zhang, Rui" <rui.zhang@...el.com>, 
	"srinivas.pandruvada@...ux.intel.com" <srinivas.pandruvada@...ux.intel.com>
Cc: "lukasz.luba@....com" <lukasz.luba@....com>, 
	"daniel.lezcano@...aro.org" <daniel.lezcano@...aro.org>, 
	"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>, 
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 1/2] thermal: intel: int340x: Add throttling control
 interface to PTC

On Mon, Jun 16, 2025 at 2:47 AM Zhang, Rui <rui.zhang@...el.com> wrote:
>
> On Fri, 2025-06-13 at 14:49 -0700, Srinivas Pandruvada wrote:
> > Firmware-based thermal temperature control loops may aggressively
> > throttle performance to prevent temperature overshoots relative to the
> > defined target temperature. This can negatively impact performance.
> > User
> > space may prefer to prioritize performance, even if it results in
> > temperature overshoots with in acceptable range.
> >
> > For example, user space might tolerate temperature overshoots when the
> > device is placed on a desk, as opposed to when it's on a lap. To
> > accommodate such scenarios, an optional attribute is provided to
> > specify
> > a tolerance level for temperature overshoots while maintaining
> > acceptable
> > performance.
> >
> > Attribute:
> > thermal_tolerance:
>
> yeah, this is much better to me.
>
> >  This attribute ranges from 0 to 7, where 0 represents
> > the most aggressive control to avoid any temperature overshoots, and 7
> > represents a more graceful approach, favoring performance even at the
> > expense of temperature overshoots.
> > Note: This level may not scale linearly. For example, a value of 3 does
> > not
> > necessarily imply a 50% improvement in performance compared to a value
> > of
> > 0.
> >
> > Signed-off-by: Srinivas Pandruvada
> > <srinivas.pandruvada@...ux.intel.com>
>
> Reviewed-by: Zhang Rui <rui.zhang@...el.com>

Applied along with the [2/2] as 6.17 material, thanks!

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ