public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
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 3/9] ACPI: processor: idle: Return failure when get lpi_state->arch_flags failed
Date: Thu, 23 Oct 2025 17:59:49 +0800	[thread overview]
Message-ID: <5caae4ef-e259-47cc-b0b7-f383dce4a334@huawei.com> (raw)
In-Reply-To: <CAJZ5v0hNj817g=rr8+YTGaeBkkfNuuU7FGuZyyb1j61BMOKTGA@mail.gmail.com>


在 2025/10/22 3:36, Rafael J. Wysocki 写道:
> On Mon, Sep 29, 2025 at 11:38 AM Huisong Li <lihuisong@huawei.com> wrote:
>> The architecture specific context loss flags is important for ARM.
>> And this flag is used to control the execution of different code
>> flows in acpi_processor_ffh_lpi_enter().
>>
>> So it is better to return failure when get lpi_state->arch_flags
>> failed.
> A failure means no idle states at all.
Actually, I didn't know why driver should continue to do cpu idle 
scaling if the idle state doesn't meet the developer's expectations.🙂
> Wouldn't it be better to skip the state with invalid arch flags?
This arch flags is important.  And acpi_processor_ffh_lpi_enter will use it.
There is no other place to verify its validity. so here do it.
This check is just to prevent potential issues in cpuidle scaling later.
>
>> Fixes: a36a7fecfe60 ("ACPI / processor_idle: Add support for Low Power Idle(LPI) states")
>> Signed-off-by: Huisong Li <lihuisong@huawei.com>
>> ---
>>   drivers/acpi/processor_idle.c | 7 +++++--
>>   1 file changed, 5 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/acpi/processor_idle.c b/drivers/acpi/processor_idle.c
>> index 681587f2614b..f36f9514b6c7 100644
>> --- a/drivers/acpi/processor_idle.c
>> +++ b/drivers/acpi/processor_idle.c
>> @@ -984,8 +984,11 @@ static int acpi_processor_evaluate_lpi(acpi_handle handle,
>>                  if (obj_get_integer(pkg_elem + 2, &lpi_state->flags))
>>                          lpi_state->flags = 0;
>>
>> -               if (obj_get_integer(pkg_elem + 3, &lpi_state->arch_flags))
>> -                       lpi_state->arch_flags = 0;
>> +               if (obj_get_integer(pkg_elem + 3, &lpi_state->arch_flags)) {
>> +                       pr_err("Get architecture specific context loss flags failed.\n");
>> +                       ret = -EINVAL;
>> +                       goto end;
>> +               }
>>
>>                  if (obj_get_integer(pkg_elem + 4, &lpi_state->res_cnt_freq))
>>                          lpi_state->res_cnt_freq = 1;
>> --
>> 2.33.0
>>

  reply	other threads:[~2025-10-23  9:59 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)
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) [this message]
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=5caae4ef-e259-47cc-b0b7-f383dce4a334@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