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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 15 Oct 2020 14:06:39 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>
Cc:     Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
        lkml <linux-kernel@...r.kernel.org>, rafael@...nel.org,
        Linux ACPI <linux-acpi@...r.kernel.org>
Subject: Re: DPTF_POWER and DPTF_PCH_FIVR

On Thu, Oct 15, 2020 at 01:31:55PM +0200, Rafael J. Wysocki wrote:
> Well, they depend on ACPI too and it doesn't look like there is anything
> more fine grained that could be used here.
> 
> Also I'm not sure if adding ACPI_DPTF (bool, disabled by default and
> depending on x86) would help a lot.

So you're saying this is going to be present in current and future
hardware so might as well enable it?

> Obviously an oversight on my part, sorry.
> 
> I think that changing it to "dptf_power" (and analogously for the FIVR
> participant driver) should work.  Srinivas?

Makes sense.

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ