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: <6b30aaf57cec5b6a72cff1f32d4fe24e47e9754b.camel@insiberia.net>
Date:   Mon, 08 Nov 2021 10:01:51 +0000
From:   Stefano Picascia <stefano.picascia@...iberia.net>
To:     Huang Rui <ray.huang@....com>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Allow selecting amd-pstate without CPU_SUP_INTEL

On Mon, 2021-11-08 at 17:13 +0800, Huang Rui wrote:
> On Sat, Nov 06, 2021 at 07:55:29PM +0800, Stefano Picascia wrote:
> > Currently, even if selected, amd-pstate is not enabled unless
> > CPU_SUP_INTEL is also selected, due to ACPI_CPPC_LIB depending on
> > SCHED_MC_PRIO, which in turn depends on CPU_SUP_INTEL
> 
> Actually, amd-pstate driver doesn't depend on SCHED_MC_PRIO. 

amd-pstate doesn't depend on SCHED_MC_PRIO, but ACPI_CPPC_LIB is only
selected when SCHED_MC_PRIO is selected. I guess the issue can be fixed
in a better way, but currently if one compiles the kernel with
CPU_SUP_AMD, but without CPU_SUP_INTEL, ends up with a non functional
amd-pstate. 

Not a problem for distro kernels I guess, but I was puzzled as I wasn't
getting amd-pstate even with a supported processor.

Regards!

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ