linux-kernel - Re: [PATCH 0/3] cpuidle: Rework the handling of the poll state

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <1350530b-bed8-ab45-d5d2-dcaf4178320d@arm.com>
Date:   Thu, 24 Aug 2017 10:48:19 +0100
From:   Sudeep Holla <sudeep.holla@....com>
To:     "Rafael J. Wysocki" <rjw@...ysocki.net>,
        Linux PM <linux-pm@...r.kernel.org>
Cc:     Sudeep Holla <sudeep.holla@....com>,
        LKML <linux-kernel@...r.kernel.org>,
        Len Brown <len.brown@...el.com>,
        Linux ACPI <linux-acpi@...r.kernel.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Jacob Pan <jacob.jun.pan@...ux.intel.com>,
        Daniel Lezcano <daniel.lezcano@...aro.org>
Subject: Re: [PATCH 0/3] cpuidle: Rework the handling of the poll state



On 23/08/17 22:18, Rafael J. Wysocki wrote:
> Hi,
> 
> On x86 the fist idle state is a polling one, but the way it is set up is far
> from straightforward and then it is avoided by governors in rather somewhat
> convoluted fashion.
> 
> Make this more clear by explicitly flagging that state as "polling" and
> checking its flag where it needs to be avoided instead of using
> arch-dependent numbering of idle states (patch [1/3]), move the
> polling state code from driver.c to a separate C file (patch [2/3]) and
> move the initialization of it from the core to the relevant cpuidle drivers -
> ACPI and intel_idle (patch [3/3]).
> 

Tested this on ARM64 platform(both DT and ACPI/LPI) and everything
continues to work fine.
Tested-by: Sudeep Holla <sudeep.holla@....com>

-- 
Regards,
Sudeep