public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: stable@vger.kernel.org,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Christian Loehle <christian.loehle@arm.com>,
	Marc Zyngier <maz@kernel.org>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1.y] cpuidle: governors: menu: Avoid using invalid recent intervals data
Date: Thu, 16 Oct 2025 10:55:25 +0200	[thread overview]
Message-ID: <2025101614-shown-handbag-58e3@gregkh> (raw)
In-Reply-To: <20251014130300.2365621-1-senozhatsky@chromium.org>

On Tue, Oct 14, 2025 at 10:03:00PM +0900, Sergey Senozhatsky wrote:
> From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
> 
> [ Upstream commit fa3fa55de0d6177fdcaf6fc254f13cc8f33c3eed ]
> 
> Marc has reported that commit 85975daeaa4d ("cpuidle: menu: Avoid
> discarding useful information") caused the number of wakeup interrupts
> to increase on an idle system [1], which was not expected to happen
> after merely allowing shallower idle states to be selected by the
> governor in some cases.
> 
> However, on the system in question, all of the idle states deeper than
> WFI are rejected by the driver due to a firmware issue [2].  This causes
> the governor to only consider the recent interval duriation data
> corresponding to attempts to enter WFI that are successful and the
> recent invervals table is filled with values lower than the scheduler
> tick period.  Consequently, the governor predicts an idle duration
> below the scheduler tick period length and avoids stopping the tick
> more often which leads to the observed symptom.
> 
> Address it by modifying the governor to update the recent intervals
> table also when entering the previously selected idle state fails, so
> it knows that the short idle intervals might have been the minority
> had the selected idle states been actually entered every time.
> 
> Fixes: 85975daeaa4d ("cpuidle: menu: Avoid discarding useful information")
> Link: https://lore.kernel.org/linux-pm/86o6sv6n94.wl-maz@kernel.org/ [1]
> Link: https://lore.kernel.org/linux-pm/7ffcb716-9a1b-48c2-aaa4-469d0df7c792@arm.com/ [2]
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Tested-by: Christian Loehle <christian.loehle@arm.com>
> Tested-by: Marc Zyngier <maz@kernel.org>
> Reviewed-by: Christian Loehle <christian.loehle@arm.com>
> Link: https://patch.msgid.link/2793874.mvXUDI8C0e@rafael.j.wysocki
> Signed-off-by: Sasha Levin <sashal@kernel.org>
> (cherry picked from commit 7337a6356dffc93194af24ee31023b3578661a5b)

You forgot to sign off on this :(


  parent reply	other threads:[~2025-10-16  8:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-14 13:03 [PATCH 6.1.y] cpuidle: governors: menu: Avoid using invalid recent intervals data Sergey Senozhatsky
2025-10-14 13:49 ` Christian Loehle
2025-10-16  8:55 ` Greg KH [this message]
2025-10-16  8:57   ` Sergey Senozhatsky
2025-10-16  9:05     ` Greg KH
2025-10-16  9:08       ` Sergey Senozhatsky
2025-10-16  9:12         ` Greg KH
2025-10-16  9:17           ` Sergey Senozhatsky

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=2025101614-shown-handbag-58e3@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=christian.loehle@arm.com \
    --cc=maz@kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=sashal@kernel.org \
    --cc=senozhatsky@chromium.org \
    --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