linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Lazar, Lijo" <lijo.lazar@amd.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
	boris.ostrovsky@oracle.com, Len Brown <lenb@kernel.org>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Mario Limonciello <mario.limonciello@amd.com>,
	"Gong, Richard" <richard.gong@amd.com>
Subject: Re: [PATCHv1] ACPI: processor idle: Allow playing dead in C3 state
Date: Wed, 29 Sep 2021 11:07:39 +0530	[thread overview]
Message-ID: <52fd74a5-c0cb-0dcc-b5da-fc84651c2253@amd.com> (raw)
In-Reply-To: <7b8a7c2a-027f-16c9-0258-d91917c39bac@amd.com>



On 9/28/2021 8:38 PM, Lazar, Lijo wrote:
> 
> 
> On 9/28/2021 7:18 PM, Rafael J. Wysocki wrote:
>> On Tue, Sep 28, 2021 at 3:00 PM Gong, Richard <richard.gong@amd.com> 
>> wrote:
>>>
>>> Hi Rafael,
>>>
>>> On 9/24/2021 11:31 AM, Rafael J. Wysocki wrote:
>>>> On Wed, Sep 22, 2021 at 3:31 PM Richard Gong <richard.gong@amd.com> 
>>>> wrote:
>>>>> When some cores are disabled on AMD platforms, the system will no 
>>>>> longer
>>>>> be able to enter suspend-to-idle s0ix.
>>>>>
>>>>> Update to allow playing dead in C3 state so that the CPUs can enter 
>>>>> the
>>>>> deepest state on AMD platforms.
>>>>>
>>>>> BugLink: 
>>>>> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.freedesktop.org%2Fdrm%2Famd%2F-%2Fissues%2F1708&amp;data=04%7C01%7Clijo.lazar%40amd.com%7C44c85e9ae1dd4bec087e08d98286aa72%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637684337168161919%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=Qoh%2BwD%2B1JzPYBc0rrGfNCdQWY1pKo8WBhLPmsmQ6G%2Bo%3D&amp;reserved=0 
>>>>>
>>>>> Suggested-by: Mario Limonciello <mario.limonciello@amd.com>
>>>>> Signed-off-by: Richard Gong <richard.gong@amd.com>
>>>>> ---
>>>>>    drivers/acpi/processor_idle.c | 3 ++-
>>>>>    1 file changed, 2 insertions(+), 1 deletion(-)
>>>>>
>>>>> diff --git a/drivers/acpi/processor_idle.c 
>>>>> b/drivers/acpi/processor_idle.c
>>>>> index f37fba9e5ba0..61d5a72d218e 100644
>>>>> --- a/drivers/acpi/processor_idle.c
>>>>> +++ b/drivers/acpi/processor_idle.c
>>>>> @@ -789,7 +789,8 @@ static int acpi_processor_setup_cstates(struct 
>>>>> acpi_processor *pr)
>>>>>                   state->enter = acpi_idle_enter;
>>>>>
>>>>>                   state->flags = 0;
>>>>> -               if (cx->type == ACPI_STATE_C1 || cx->type == 
>>>>> ACPI_STATE_C2) {
>>>>> +               if (cx->type == ACPI_STATE_C1 || cx->type == 
>>>>> ACPI_STATE_C2
>>>>> +                       || cx->type == ACPI_STATE_C3) {
>>>>>                           state->enter_dead = acpi_idle_play_dead;
>>>>>                           drv->safe_state_index = count;
>>>>>                   }
>>>>> -- 
>>>> Tentatively applied as 5.16 material, but have you done any research
>>>> on why this restriction has been there in the first place?
>>>
>>> Yes, we need this change to align with the updated firmware on AMD
>>> platforms.
>>
>> Well, it wouldn't be necessary to change the code otherwise.
>>
>> Still, without the patch it is not allowed to play dead in deep idle
>> states (C3 type) and do you know why?
>>
> 
> Found the original patch thread, unfortunately there is no discussion on 
> why C3 was skipped or not allowed - 
> https://www.spinics.net/lists/linux-pm/msg27003.html
> 
> Maybe, Intel CPU offlining worked through MWAITs and AMD bothered only 
> till C2.
> 

Hi Boris/Len,

Apologies to barge in. This is regarding the patch you added years back 
- https://www.spinics.net/lists/linux-pm/msg27003.html

Do you recall why C3 was not considered for offline/play dead scenarios 
in the original patch?

For newer AMD processors, power management controller expects all cores 
to request C3 as a precondition for s2idle. When cores are offlined, 
they request only C2 and that prevents s2idle in such cases.

This new patch series is to consider C3 also for offline purpose.

https://lore.kernel.org/linux-acpi/7b8a7c2a-027f-16c9-0258-d91917c39bac@amd.com/T/#ma818870a8272a3755de896dd79d478cf944d1555

Please take a look and also at the questions from Rafael.

Thanks,
Lijo

>> Or IOW how likely is this change to break anything on legacy platforms?
>>

  reply	other threads:[~2021-09-29  5:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-22 13:31 [PATCHv1] ACPI: processor idle: Allow playing dead in C3 state Richard Gong
2021-09-24 16:31 ` Rafael J. Wysocki
2021-09-28 13:00   ` Gong, Richard
2021-09-28 13:48     ` Rafael J. Wysocki
2021-09-28 15:08       ` Lazar, Lijo
2021-09-29  5:37         ` Lazar, Lijo [this message]
2021-09-29 14:09           ` Boris Ostrovsky
2021-09-29 14:45             ` 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=52fd74a5-c0cb-0dcc-b5da-fc84651c2253@amd.com \
    --to=lijo.lazar@amd.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=rafael@kernel.org \
    --cc=richard.gong@amd.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).