linux-kernel - Re: [PATCH] ACPI: kernel-parameters.txt : Add intel_idle.max

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]

Date:	Fri, 16 Dec 2011 13:21:28 +0900
From:	Masanari Iida <standby24x7@...il.com>
To:	Thomas Renninger <trenn@...e.de>
Cc:	linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
	rdunlap@...otime.net, lenb@...nel.org
Subject: Re: [PATCH] ACPI: kernel-parameters.txt : Add intel_idle.max_cstate

2011/12/16 Thomas Renninger <trenn@...e.de>:
> On Wednesday, December 14, 2011 05:18:52 PM Masanari Iida wrote:
>> Add missing intel_idle.max_cstate in kernel-parameters.txt
> I wonder whether this one should get documented at all.
>
My opinion is, as long as the kernel parameter is available,
we should document it.  And if developer want to guide the user to use
cpuidle.max_cstate, we should document so.

> Better would be to work towards a general cpuidle.max_state=
> param which deprecates processor.max_cstate= (acpi_idle driver) and
> intel_idle.max_cstate= and enables this functionality for all
> other cpuidle drivers out there as well.
>
cpuidle.max_state is also not in the kernel-parameters.txt,
Separate patch need to be created.

> Something to turn off intel_idle driver and favor the acpi_idle
> driver for debugging would still be needed then.
>
This patch explains how to disable intel_idle.
Although processor.max_cstate=0 sets cstate to 0,
but similar option intel_idle.max_cstate=0 didn't set cstate to 0.
This is confusing for the users.
This is the reason why I wanted to document it.

Masanari Iida
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/