From: Prarit Bhargava <prarit@redhat.com>
To: David Arcari <darcari@redhat.com>,
dedekind1@gmail.com, linux-pm@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>,
Jacob Pan <jacob.jun.pan@linux.intel.com>,
Len Brown <lenb@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] intel_idle: introduce 'use_acpi_cst' module parameter
Date: Tue, 4 Feb 2025 08:04:27 -0500 [thread overview]
Message-ID: <b50ade64-21ea-4420-a7ec-5e17ea7f6af7@redhat.com> (raw)
In-Reply-To: <afbe2137-398b-4053-93e7-2a03aeb32220@redhat.com>
On 2/4/25 7:52 AM, David Arcari wrote:
>
> Hi Artem,
>
> On 2/4/25 7:23 AM, Artem Bityutskiy wrote:
>> Hi David,
>>
>> On Tue, 2025-01-28 at 09:11 -0500, David Arcari wrote:
>>
>>> +The ``use_acpi_cst`` module parameter (recognized by ``intel_idle``
>>> if the
>>> +kernel has been configured with ACPI support) can be set to make the
>>> driver
>>> +ignore the per cpu idle states in lieu of ACPI idle states.
>>> ``use_acpi_cst``
>>> +has no effect if ``no_acpi`` is set).
>>
>> With this change, there will be three parameters:
>>
>> * no_acpi
>> * use_acpi
>> * use_acpi_cst
>>
>> I would like to make the naming as intuitive as possible. We do not
>> rename the
>> first 2, but for the 3rd one, I think "force_acpi" would be a better
>> name. Or
>> perhaps "no_native"?
>
> The problem with force_acpi is it is very similar to force_use_acpi
> which is what intel_idle.c uses internally:
>
Given that @Artem is suggesting we change the names of things -- perhaps
we should fix "force_use_acpi" as well?
P.
> drivers/idle/intel_idle.c:module_param_named(use_acpi, force_use_acpi,
> bool, 0444);
>
> That said, I am not attached to the 'use_acpi_cst' parameter name.
>
>>
>> * no_acpi - Do not use ACPI at all. Only native mode is available, no
>> ACPI mode.
>> * use_acpi - No-op in ACPI mode, consult ACPI tables for C-states on/off
>> status in native mode.
>> * force_acpi (or no_native?) - Work only in ACPI mode, no native mode
>> available
>> (ignore all custom tables).
>>
>> Additionally, I think we should enhance the documentation for
>> 'no_acpi' and
>> 'use_acpi' while we're at it. Otherwise, it is hard to distinguish
>> between these
>> three options. Would you consider another patch that improves the
>> documentation
>> for 'no_acpi' and 'use_acpi', and then adds the third parameter?
>
> I'm happy to resubmit. I guess I could use 'no_native' for the new
> parameter and then update the documentation as you suggest above.
>
> Does that work?
>
>>
>> Thanks, Artem!
>>
>
> Best,
> -DA
>
next prev parent reply other threads:[~2025-02-04 13:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 14:11 [PATCH] intel_idle: introduce 'use_acpi_cst' module parameter David Arcari
2025-02-04 12:23 ` Artem Bityutskiy
2025-02-04 12:52 ` David Arcari
2025-02-04 13:04 ` Prarit Bhargava [this message]
2025-02-04 15:21 ` Rafael J. Wysocki
2025-02-04 16:30 ` Artem Bityutskiy
2025-02-04 17:33 ` Rafael J. Wysocki
2025-02-05 12:09 ` David Arcari
2025-02-04 16:26 ` Artem Bityutskiy
2025-02-06 16:40 ` [PATCH v2] intel_idle: introduce 'no_native' " David Arcari
2025-02-07 15:55 ` Artem Bityutskiy
2025-02-07 17:13 ` David Arcari
2025-02-08 10:37 ` Artem Bityutskiy
2025-02-08 19:56 ` David Arcari
2025-02-09 9:08 ` Artem Bityutskiy
2025-02-11 13:27 ` [PATCH v3] " David Arcari
2025-02-12 7:04 ` Artem Bityutskiy
2025-02-12 10:09 ` kernel test robot
2025-02-12 11:32 ` Artem Bityutskiy
2025-02-12 12:41 ` David Arcari
2025-02-12 12:46 ` Artem Bityutskiy
2025-02-12 12:53 ` David Arcari
2025-02-12 12:49 ` Artem Bityutskiy
2025-02-13 11:49 ` kernel test robot
2025-02-13 16:07 ` [PATCH v4] " David Arcari
2025-02-18 19:57 ` Rafael J. Wysocki
2025-02-20 12:50 ` Artem Bityutskiy
2025-02-19 21:27 ` Rafael J. Wysocki
2025-02-20 12:21 ` David Arcari
2025-02-20 12:23 ` Rafael J. Wysocki
2025-02-20 15:11 ` [PATCH v5] " David Arcari
2025-02-20 20:02 ` 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=b50ade64-21ea-4420-a7ec-5e17ea7f6af7@redhat.com \
--to=prarit@redhat.com \
--cc=corbet@lwn.net \
--cc=darcari@redhat.com \
--cc=dedekind1@gmail.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
/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