linux-stable.git/drivers/powercap, branch linux-5.17.y

powercap/dtpm_cpu: Reset per_cpu variable in the release function

2022-04-08T11:58:37+00:00

[ Upstream commit 0aea2e4ec2a2bfa2d7e8820e37ba5b5ce04f20a5 ]

The release function does not reset the per cpu variable when it is
called. That will prevent creation again as the variable will be
already from the previous creation.

Fix it by resetting them.

Signed-off-by: Daniel Lezcano 
Reviewed-by: Ulf Hansson 
Link: https://lore.kernel.org/r/20220130210210.549877-2-daniel.lezcano@linaro.org
Signed-off-by: Sasha Levin

Merge back earlier power capping changes for v5.17

2021-12-27T15:51:12+00:00

powercap/drivers/dtpm: Reduce trace verbosity

2021-12-23T15:57:36+00:00

The traces when registering a powerzone is at the pr_info level and
should be changed to pr_debug as requested by Greg-KH.

Cc: Greg KH 
Reviewed-by: Greg Kroah-Hartman 
Link: https://lkml.kernel.org/r/YGAnRx8SiZHFPpY6@kroah.com
Signed-off-by: Daniel Lezcano 
Link: https://lore.kernel.org/r/20211123101601.2433340-2-daniel.lezcano@linaro.org

powercap: fix typo in a comment in idle_inject.c

2021-12-17T15:30:19+00:00

Drop superfluous "the" from the comment in line 15.

Signed-off-by: Jason Wang 
[ rjw: Subject edit, new changelog ]
Signed-off-by: Rafael J. Wysocki

powercap: intel_rapl: support new layout of Psys PowerLimit Register on SPR

2021-12-17T15:13:14+00:00

On Sapphire Rapids, the layout of the Psys domain Power Limit Register
is different from from what it was before.

Enhance the code to support the new Psys PL register layout.

Signed-off-by: Zhang Rui 
Reported-and-tested-by: Alkattan Dana 
[ rjw: Subject and changelog edits ]
Signed-off-by: Rafael J. Wysocki

powercap: DTPM: Drop unused local variable from init_dtpm()

2021-12-03T16:51:59+00:00

The dtpm_descr variable in init_dtpm() is not used after commit
f751db8adaea ("powercap/drivers/dtpm: Disable DTPM at boot time"),
so drop it.

Fixes: f751db8adaea ("powercap/drivers/dtpm: Disable DTPM at boot time")
Reported-by: Stephen Rothwell 
Signed-off-by: Rafael J. Wysocki

powercap/drivers/dtpm: Disable DTPM at boot time

2021-12-01T18:55:34+00:00

The DTPM framework misses a mechanism to set it up. That is currently
under review but will come after the next cycle.

As the distro are enabling all the kernel options, the DTPM framework
is enabled on platforms where the energy model is not implemented,
thus making the framework inconsistent and disrupting the CPU
frequency scaling service.

Remove the initialization at boot time as a hot fix.

Fixes: 7a89d7eacf8e ("powercap/drivers/dtpm: Simplify the dtpm table")
Signed-off-by: Daniel Lezcano 
Reported-By: Doug Smythies 
Tested-By: Doug Smythies 
Signed-off-by: Rafael J. Wysocki

powercap: DTPM: Fix suspend failure and kernel warning

2021-11-10T20:18:14+00:00

When the ENERGY_MODEL and DTPM_CPU are enabled but actually without
any energy model, at cpu hotplug time, the dead cpuhp callback fails
leading to the warning.

Actually, the check could be simplified and we only do an action if
the dtpm cpu is enabled, otherwise we bail out without error.

Fixes: 7a89d7eacf8e ("powercap/drivers/dtpm: Simplify the dtpm table")
Reported-by: Kenneth R. Crudup 
Tested-by: Kenneth R. Crudup 
Reported-by: kernel test robot 
Signed-off-by: Daniel Lezcano 
Signed-off-by: Rafael J. Wysocki

powercap/drivers/dtpm: Fix power limit initialization

2021-10-21T14:03:31+00:00

When a DTPM node is registered its power limit must be initialized to
the power max.

Signed-off-by: Daniel Lezcano 
Link: https://lore.kernel.org/r/20210318205238.21937-1-daniel.lezcano@linaro.org

powercap/drivers/dtpm: Scale the power with the load

2021-10-21T14:03:31+00:00

Currently the power consumption is based on the current OPP power
assuming the entire performance domain is fully loaded.

That gives very gross power estimation and we can do much better by
using the load to scale the power consumption.

Use the utilization to normalize and scale the power usage over the
max possible power.

Tested on a rock960 with 2 big CPUS, the power consumption estimation
conforms with the expected one.

Before this change:

~$ ~/dhrystone -t 1 -l 10000&
~$ cat /sys/devices/virtual/powercap/dtpm/dtpm:0/dtpm:0:1/constraint_0_max_power_uw
2260000

After this change:

~$ ~/dhrystone -t 1 -l 10000&
~$ cat /sys/devices/virtual/powercap/dtpm/dtpm:0/dtpm:0:1/constraint_0_max_power_uw
1130000

~$ ~/dhrystone -t 2 -l 10000&
~$ cat /sys/devices/virtual/powercap/dtpm/dtpm:0/dtpm:0:1/constraint_0_max_power_uw
2260000

Signed-off-by: Daniel Lezcano 
Reviewed-by: Lukasz Luba 
Link: https://lore.kernel.org/r/20210312130411.29833-5-daniel.lezcano@linaro.org