linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux PM <linux-pm@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Anna-Maria Behnsen <anna-maria@linutronix.de>,
	Frederic Weisbecker <frederic@kernel.org>,
	Kajetan Puchalski <kajetan.puchalski@arm.com>
Subject: [PATCH v3 0/3] cpuidle: teo: Avoid stopping scheduler tick too often
Date: Mon, 31 Jul 2023 20:49:33 +0200	[thread overview]
Message-ID: <4515817.LvFx2qVVIh@kreacher> (raw)

Hi Folks,

Patch [1/3] in this series is a v3 of this patch posted last week:

https://lore.kernel.org/linux-pm/4506480.LvFx2qVVIh@kreacher/

Patch [2/3] (this is the second version of it) addresses some bail out paths
in teo_select() in which the scheduler tick may be stopped unnecessarily too.

Patch [3/3] replaces a structure field with a local variable (while at it)
and it is the same as its previous version.

According to this message:

https://lore.kernel.org/linux-pm/CAJZ5v0jJxHj65r2HXBTd3wfbZtsg=_StzwO1kA5STDnaPe_dWA@mail.gmail.com/

this series significantly reduces the number of cases in which the governor
requests stopping the tick when the selected idle state is shallow, which is
incorrect.

Thanks!




             reply	other threads:[~2023-07-31 19:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31 18:49 Rafael J. Wysocki [this message]
2023-07-31 18:56 ` [PATCH v3 1/3] cpuidle: teo: Update idle duration estimate when choosing shallower state Rafael J. Wysocki
2023-07-31 19:03 ` [PATCH v3 2/3] cpuidle: teo: Avoid stopping the tick unnecessarily when bailing out Rafael J. Wysocki
2023-07-31 19:04 ` [PATCH v3 3/3] cpuidle: teo: Drop utilized from struct teo_cpu Rafael J. Wysocki
2023-08-01 21:53 ` [PATCH v3 0/3] cpuidle: teo: Avoid stopping scheduler tick too often Kajetan Puchalski
2023-08-02 12:20   ` 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=4515817.LvFx2qVVIh@kreacher \
    --to=rjw@rjwysocki.net \
    --cc=anna-maria@linutronix.de \
    --cc=frederic@kernel.org \
    --cc=kajetan.puchalski@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).