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] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 11 Apr 2019 22:44:29 +0200
From:   "Rafael J. Wysocki" <>
To:     Ulf Hansson <>
Cc:     "Rafael J . Wysocki" <>,
        Linux PM <>,
        Frederic Weisbecker <>,
        Thomas Gleixner <>,
        Sudeep Holla <>,
        Lorenzo Pieralisi <>,
        Mark Rutland <>,
        Daniel Lezcano <>,
        "Raju P . L . S . S . S . N" <>,
        Stephen Boyd <>,
        Tony Lindgren <>,
        Kevin Hilman <>,
        Lina Iyer <>,
        Viresh Kumar <>,
        Vincent Guittot <>,
        Geert Uytterhoeven <>,
        Linux ARM <>,
        linux-arm-msm <>,
        Linux Kernel Mailing List <>,
        "Rafael J . Wysocki" <>
Subject: Re: [PATCH v14 4/4] PM / Domains: Add genpd governor for CPUs

On Thu, Apr 11, 2019 at 8:17 PM Ulf Hansson <> wrote:
> After some preceding changes, PM domains managed by genpd may contain
> CPU devices, so idle state residency values should be taken into
> account during the state selection process. [The residency value is
> the minimum amount of time to be spent by a CPU (or a group of CPUs)
> in an idle state in order to save more energy than could be saved
> by picking up a shallower idle state.]
> For this purpose, add a new genpd governor, pm_domain_cpu_gov, to be
> used for selecting idle states of PM domains with CPU devices attached
> either directly or through subdomains.
> The new governor computes the minimum expected idle duration for all
> online CPUs attached to a PM domain and its subdomains.  Next, it
> finds the deepest idle state whose target residency is within the
> expected idle duration and selects it as the target idle state of
> the domain.
> It should be noted that the minimum expected idle duration computation
> is based on the closest timer event information stored in the per-CPU
> variables cpuidle_devices for all of the CPUs in the domain.  That
> needs to be revisited in future, as obviously there are other reasons
> why a CPU may be woken up from idle.
> Co-developed-by: Lina Iyer <>
> Acked-by: Daniel Lezcano <>
> Signed-off-by: Ulf Hansson <>
> [ rjw: Changelog ]
> Signed-off-by: Rafael J. Wysocki <>

Applied instead of the previous version, thanks!

Powered by blists - more mailing lists