linux-kernel - Re: [PATCH] intel_idle: introduce 'use_acpi

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: <c3f03a5837e191c5371593ac0a0e3c56e4204567.camel@gmail.com>
Date: Tue, 04 Feb 2025 18:30:41 +0200
From: Artem Bityutskiy <dedekind1@...il.com>
To: "Rafael J. Wysocki" <rafael@...nel.org>, David Arcari
 <darcari@...hat.com>
Cc: linux-pm@...r.kernel.org, Jonathan Corbet <corbet@....net>, Len Brown
	 <lenb@...nel.org>, Prarit Bhargava <prarit@...hat.com>, 
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] intel_idle: introduce 'use_acpi_cst' module parameter

On Tue, 2025-02-04 at 16:21 +0100, Rafael J. Wysocki wrote:
> But it could be something like "prefer_acpi" as far as I'm concerned.

When I see "prefer_acpi", my intuition tells that it is just a preference:
"prefer ACPI, but may be native too". But I understood that the patch is about
"only ACPI and never native".

The reasons I suggested "no_native":
* Sort of consistent with "no_acpi"
* Suggests that native won't work.

Thanks.