From: "lihuisong (C)" <lihuisong@huawei.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: <lenb@kernel.org>, <linux-acpi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <Sudeep.Holla@arm.com>,
<linuxarm@huawei.com>, <jonathan.cameron@huawei.com>,
<zhanjie9@hisilicon.com>, <zhenglifeng1@huawei.com>,
<yubowen8@huawei.com>
Subject: Re: [PATCH v1 2/9] ACPI: processor: idle: Return failure if entry method is not buffer or integer type
Date: Fri, 24 Oct 2025 17:25:35 +0800 [thread overview]
Message-ID: <a577bfd3-a4b8-4d06-b95b-a78b2916b8a4@huawei.com> (raw)
In-Reply-To: <CAJZ5v0jg5RGi-+i3LtwK6U8m+_C5Rs4OuRTBLTGi6g0aRq3LBQ@mail.gmail.com>
在 2025/10/23 18:07, Rafael J. Wysocki 写道:
> On Thu, Oct 23, 2025 at 11:25 AM lihuisong (C) <lihuisong@huawei.com> wrote:
>>
>> 在 2025/10/22 3:34, Rafael J. Wysocki 写道:
>>> On Mon, Sep 29, 2025 at 11:38 AM Huisong Li <lihuisong@huawei.com> wrote:
>>>> According to ACPI spec, entry method in LPI sub-package must be buffer
>>>> or integer. However, acpi_processor_evaluate_lpi() regeards it as success
>>>> and treat it as an effective LPI state.
>>> Is that the case? AFAICS, it just gets to the next state in this case
>>> and what's wrong with that?
>> The flatten_lpi_states() would consider the state with illegal entry
>> method sub-package as a valid one
>> if the flag of this state is enabled(ACPI_LPI_STATE_FLAGS_ENABLED is set).
>> And then cpuidle governor would use it because the caller of
>> acpi_processor_ffh_lpi_probe() also don't see the return value.
> So the problem appears to be that lpi_state increments in every step
> of the loop, but it should only increment if the given state is valid.
Yes,
So set the flag of the state with illegal entry method sub-package to
zero so that this invalid LPI state will be skiped in
flatten_lpi_states(), ok?
next prev parent reply other threads:[~2025-10-24 9:25 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 9:37 [PATCH v1 0/9] ACPI: processor: idle: enhance and cleancode for cpuidle state Huisong Li
2025-09-29 9:37 ` [PATCH v1 1/9] ACPI: processor: idle: raise up log level when evaluate LPI failed Huisong Li
2025-10-21 19:29 ` Rafael J. Wysocki
2025-10-23 9:09 ` lihuisong (C)
2025-09-29 9:37 ` [PATCH v1 2/9] ACPI: processor: idle: Return failure if entry method is not buffer or integer type Huisong Li
2025-10-21 19:34 ` Rafael J. Wysocki
2025-10-23 9:25 ` lihuisong (C)
2025-10-23 10:07 ` Rafael J. Wysocki
2025-10-24 9:25 ` lihuisong (C) [this message]
2025-10-26 12:35 ` Rafael J. Wysocki
2025-09-29 9:37 ` [PATCH v1 3/9] ACPI: processor: idle: Return failure when get lpi_state->arch_flags failed Huisong Li
2025-10-21 19:36 ` Rafael J. Wysocki
2025-10-23 9:59 ` lihuisong (C)
2025-10-23 10:09 ` Rafael J. Wysocki
2025-10-24 9:27 ` lihuisong (C)
2025-09-29 9:37 ` [PATCH v1 4/9] ACPI: processor: idle: Move the initialization of state->flags to acpi_processor_setup_cstates Huisong Li
2025-10-22 14:49 ` Rafael J. Wysocki
2025-09-29 9:37 ` [PATCH v1 5/9] ACPI: processor: idle: Add the verification of processor FFH LPI state Huisong Li
2025-10-21 19:42 ` Rafael J. Wysocki
2025-10-23 10:17 ` lihuisong (C)
2025-10-23 10:35 ` Rafael J. Wysocki
2025-10-24 9:40 ` lihuisong (C)
2025-10-26 12:40 ` Rafael J. Wysocki
2025-10-27 1:42 ` lihuisong (C)
2025-10-27 12:28 ` Rafael J. Wysocki
2025-10-28 12:45 ` lihuisong (C)
2025-10-28 14:10 ` Rafael J. Wysocki
2025-09-29 9:37 ` [PATCH v1 6/9] ACPI: processor: idle: Do not change power states if get power info failed Huisong Li
2025-10-21 19:49 ` Rafael J. Wysocki
2025-10-24 9:10 ` lihuisong (C)
2025-10-26 12:34 ` Rafael J. Wysocki
2025-10-27 3:01 ` lihuisong (C)
2025-10-27 12:31 ` Rafael J. Wysocki
2025-09-29 9:37 ` [PATCH v1 7/9] ACPI: processor: idle: Remove died codes about the verification of cstate count Huisong Li
2025-10-21 19:51 ` Rafael J. Wysocki
2025-10-23 10:19 ` lihuisong (C)
2025-09-29 9:37 ` [PATCH v1 8/9] ACPI: processor: idle: Redefine setup idle functions to void Huisong Li
2025-09-29 9:37 ` [PATCH v1 9/9] ACPI: processor: idle: Redefine acpi_processor_setup_cpuidle_dev " Huisong Li
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=a577bfd3-a4b8-4d06-b95b-a78b2916b8a4@huawei.com \
--to=lihuisong@huawei.com \
--cc=Sudeep.Holla@arm.com \
--cc=jonathan.cameron@huawei.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=rafael@kernel.org \
--cc=yubowen8@huawei.com \
--cc=zhanjie9@hisilicon.com \
--cc=zhenglifeng1@huawei.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