public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Limonciello, Mario" <Mario.Limonciello@amd.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: Fix issues caused by lack of x86 LPI support
Date: Thu, 14 Apr 2022 12:56:38 +0200	[thread overview]
Message-ID: <Ylf95jt6GSjbJeO+@kroah.com> (raw)
In-Reply-To: <BL1PR12MB515758FA1BFA7C94812B88A3E2ED9@BL1PR12MB5157.namprd12.prod.outlook.com>

On Tue, Apr 12, 2022 at 10:09:30PM +0000, Limonciello, Mario wrote:
> [Public]
> 
> Hi,
> 
> There are a variety of x86 systems that advertise LPI support and as part of negotiation with firmware they don't end up using C-states
> in certain circumstances.  This leads to higher runtime power consumption and also failure to enter s2idle. 
> 
> In mainline there have been changes to block that behavior.  Can you please backport these two commits from mainline?
> commit 01f6c7338ce267959975da65d86ba34f44d54220 ("cpuidle: PSCI: Move the `has_lpi` check to the beginning of the function")
> commit eb087f305919ee8169ad65665610313e74260463 ("ACPI: processor idle: Check for architectural support for LPI")
> 
> This should go to 5.15.y and later stable kernels.

Queued for 5.4 and newer kernels.  If you want this backported to older
ones, please provide a working set of patches.

thanks,

greg k-h

      reply	other threads:[~2022-04-14 10:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12 22:09 Fix issues caused by lack of x86 LPI support Limonciello, Mario
2022-04-14 10:56 ` Greg KH [this message]

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=Ylf95jt6GSjbJeO+@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Mario.Limonciello@amd.com \
    --cc=stable@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