From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux PM <linux-pm@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
Len Brown <len.brown@intel.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Len Brown <lenb@kernel.org>
Subject: [PATCH v1 00/10] cpuidle: intel_idle: Use ACPI _CST to get idle states information
Date: Fri, 13 Dec 2019 10:09:40 +0100 [thread overview]
Message-ID: <3950312.2WmFeOdZGY@kreacher> (raw)
Hi All,
The RFC of this does not seem to have attracted much attention, so here goes
the first non-RFC revision.
The purpose of this set of patches is to allow the intel_idle driver to use
C-states information from ACPI _CST on systems where the processor is not
recognized by it.
The first five patches are preparatory (please look into the changelogs for
details) and are not expected to make any functional difference.
Patch [06/10] adds ACPI _CST support to intel_idle so that _CST is used when
the driver does not have a dedicated list of C-states for the given processor.
Patch [07/10] is an update of https://patchwork.kernel.org/patch/11256815/.
Patch [08/10] changes intel_idle to also use ACPI _CST in specific cases when
there is a tables of C-states for the given processor in the driver (it will
use the _CST information to decide which C-state to enable by default then).
Patch [09/10] adds a module parameter called "no_acpi" that can be used to
prevent intel_idle from using ACPI _CST via the kernel command line.
Finally, the last patch makes intel_idle use ACPI _CST, if available, on all
server systems supported by it.
This has been lightly tested on a Dell XPS13 9360 (with an additional patch to
set use_acpi for Kaby Lake). The difference between using the idle states list
from _CST and the built-in one generally appears to be that in the latter case
the processor spends more time in package C-state when the system is idle.
If there are any concerns about this series, please let me know.
For easier access, the patches are available from the intel_idle+acpi branch
in the linux-pm.git tree.
Thanks,
Rafael
next reply other threads:[~2019-12-13 9:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 9:09 Rafael J. Wysocki [this message]
2019-12-13 9:11 ` [PATCH v1 01/10] ACPI: processor: Export function to claim _CST control Rafael J. Wysocki
2019-12-13 9:12 ` [PATCH v1 02/10] ACPI: processor: Introduce acpi_processor_evaluate_cst() Rafael J. Wysocki
2019-12-13 9:14 ` [PATCH v1 03/10] ACPI: processor: Clean up acpi_processor_evaluate_cst() Rafael J. Wysocki
2019-12-13 9:15 ` [PATCH v1 04/10] ACPI: processor: Export acpi_processor_evaluate_cst() Rafael J. Wysocki
2019-12-13 9:16 ` [PATCH v1 05/10] intel_idle: Refactor intel_idle_cpuidle_driver_init() Rafael J. Wysocki
2019-12-13 9:20 ` [PATCH v1 06/10] intel_idle: Use ACPI _CST for processor models without C-state tables Rafael J. Wysocki
2019-12-13 9:22 ` [PATCH v1 07/10] cpuidle: Allow idle states to be disabled by default Rafael J. Wysocki
2019-12-13 9:24 ` [PATCH v1 08/10] intel_idle: Allow ACPI _CST to be used for selected known processors Rafael J. Wysocki
2019-12-13 9:24 ` [PATCH v1 09/10] intel_idle: Add module parameter to prevent ACPI _CST from being used Rafael J. Wysocki
2019-12-13 9:27 ` [PATCH v1 10/10] intel_idle: Use ACPI _CST on server systems Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3950312.2WmFeOdZGY@kreacher \
--to=rjw@rjwysocki.net \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).