From: Heiko Carstens <hca@linux.ibm.com>
To: Mete Durlu <meted@linux.ibm.com>
Cc: Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Anna-Maria Behnsen <anna-maria@linutronix.de>,
Frederic Weisbecker <frederic@kernel.org>,
Ingo Molnar <mingo@kernel.org>, Thomas Gleixner <tglx@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@kernel.org>,
Christian Loehle <christian.loehle@arm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Ilya Leoshkevich <iii@linux.ibm.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v3 4/5] s390/idle: Introduce cpuidle for s390
Date: Fri, 19 Jun 2026 10:01:48 +0200 [thread overview]
Message-ID: <20260619080148.18590A1e-hca@linux.ibm.com> (raw)
In-Reply-To: <20260618-idledriver-v3-4-684061eecbcb@linux.ibm.com>
On Thu, Jun 18, 2026 at 02:00:18PM +0200, Mete Durlu wrote:
> Introduce generic cpuidle driver on s390. Use a two stage approach to
> handle idle scenarios and use idle governor for idle stage selection.
> Two stages are, from shallow to deep, idle polling and enabled wait.
>
> Suggested-by: Christian Borntraeger <borntraeger@linux.ibm.com>
> Suggested-by: Heiko Carstens <hca@linux.ibm.com>
> Signed-off-by: Mete Durlu <meted@linux.ibm.com>
> ---
> MAINTAINERS | 8 +++
> arch/s390/Kconfig | 5 ++
> drivers/cpuidle/Kconfig | 5 ++
> drivers/cpuidle/Kconfig.s390 | 11 ++++
> drivers/cpuidle/Makefile | 4 ++
> drivers/cpuidle/cpuidle-s390.c | 115 +++++++++++++++++++++++++++++++++++++++++
> 6 files changed, 148 insertions(+)
...
> +static void __init s390_cpuidle_ew_tune(void)
> +{
> + struct cpuidle_state *state = &s390_cpuidle_driver.states[1];
> +
> + if (machine_is_lpar()) {
> + state->target_residency = 5;
> + state->exit_latency = 5;
> + } else {
> + state->target_residency = 1;
> + state->exit_latency = 1;
> + }
> +}
My Reviewed-by from the previous version still stands. However minor thing is
that this function should be renamed to something like s390_cpuidle_ew_init()
or s390_cpuidle_ew_setup().
But that's something Alexander can do when applying. Or it stays like it
is. Not too important.
Anyway:
Reviewed-by: Heiko Carstens <hca@linux.ibm.com>
next prev parent reply other threads:[~2026-06-19 8:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 12:00 [PATCH v3 0/5] s390/idle: CPU idle driver Mete Durlu
2026-06-18 12:00 ` [PATCH v3 1/5] s390/tick: Remove CIF_NOHZ_DELAY flag Mete Durlu
2026-06-18 12:00 ` [PATCH v3 2/5] tick: Remove arch_needs_cpu Mete Durlu
2026-06-18 12:00 ` [PATCH v3 3/5] s390: Enable TIF_POLLING_NRFLAG Mete Durlu
2026-06-18 12:00 ` [PATCH v3 4/5] s390/idle: Introduce cpuidle for s390 Mete Durlu
2026-06-18 14:41 ` Christian Loehle
2026-06-18 14:47 ` Mete Durlu
2026-06-18 16:06 ` Christian Loehle
2026-06-19 8:01 ` Heiko Carstens [this message]
2026-06-18 12:00 ` [PATCH v3 5/5] s390/configs: Enable cpuidle driver on s390 Mete Durlu
2026-06-18 13:18 ` Christian Borntraeger
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=20260619080148.18590A1e-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=anna-maria@linutronix.de \
--cc=borntraeger@linux.ibm.com \
--cc=christian.loehle@arm.com \
--cc=daniel.lezcano@kernel.org \
--cc=frederic@kernel.org \
--cc=gor@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=meted@linux.ibm.com \
--cc=mingo@kernel.org \
--cc=rafael@kernel.org \
--cc=svens@linux.ibm.com \
--cc=tglx@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