linux-kernel - Re: [PATCH] platform/x86: intel_turbo_max_3: Remove restriction for HWP platforms

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: <7791d2f2-3a74-6dee-7055-feeaa6bbe2d8@linux.intel.com>
Date:   Wed, 14 Feb 2018 11:29:48 -0800
From:   Arjan van de Ven <arjan@...ux.intel.com>
To:     Andy Shevchenko <andy.shevchenko@...il.com>,
        Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>
Cc:     Darren Hart <dvhart@...radead.org>,
        Andy Shevchenko <andy@...radead.org>,
        Platform Driver <platform-driver-x86@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] platform/x86: intel_turbo_max_3: Remove restriction for
 HWP platforms

On 2/14/2018 11:29 AM, Andy Shevchenko wrote:
> On Mon, Feb 12, 2018 at 9:50 PM, Srinivas Pandruvada
> <srinivas.pandruvada@...ux.intel.com> wrote:
>> On systems supporting HWP (Hardware P-States) mode, we expected to
>> enumerate core priority via ACPI-CPPC tables. Unfortunately deployment of
>> TURBO 3.0 didn't use this method to show core priority. So users are not
>> able to utilize this feature in HWP mode.
>>
>> So remove the loading restriction of this driver for HWP enabled systems.
>> Even if there are some systems, which are providing the core priority via
>> ACPI CPPC, this shouldn't cause any conflict as the source of priority
>> definition is same.
>>
> 
> Pushed to my review and testing queue, thanks!
> 
> P.S. Should it go to stable?

older stable at least did not have the problem