From: Christian Loehle <christian.loehle@arm.com>
To: Mete Durlu <meted@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@kernel.org>,
Anna-Maria Behnsen <anna-maria@linutronix.de>,
Frederic Weisbecker <frederic@kernel.org>,
Ingo Molnar <mingo@kernel.org>, Thomas Gleixner <tglx@kernel.org>
Cc: Ilya Leoshkevich <iii@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
linux-s390 <linux-s390@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/5] s390/idle: Introduce cpuidle for s390
Date: Tue, 9 Jun 2026 09:12:47 +0100 [thread overview]
Message-ID: <5d9a3d2e-f083-49d4-a311-7801e70ac1a2@arm.com> (raw)
In-Reply-To: <20260609075213.31094-5-meted@linux.ibm.com>
On 6/9/26 08:52, Mete Durlu wrote:
> Introduce generic cpuidle driver on s390. Use a two stage approach to
> handle idle scenarios and use TEO 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>
> ---
> arch/s390/Kconfig | 5 ++
> drivers/cpuidle/Kconfig | 5 ++
> drivers/cpuidle/Kconfig.s390 | 12 ++++
> drivers/cpuidle/Makefile | 4 ++
> drivers/cpuidle/cpuidle-s390.c | 104 +++++++++++++++++++++++++++++++++
> 5 files changed, 130 insertions(+)
> create mode 100644 drivers/cpuidle/Kconfig.s390
> create mode 100644 drivers/cpuidle/cpuidle-s390.c
Since this will be hard for anybody without the hardware to maintain,
would you maintain it? Or the existing s390 maintainers?
If either then please also modify MAINTAINERS to reflect that.
next prev parent reply other threads:[~2026-06-09 8:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 7:52 [PATCH 0/5] s390/idle: CPU idle driver Mete Durlu
2026-06-09 7:52 ` [PATCH 1/5] s390/tick: Remove CIF_NOHZ_DELAY flag Mete Durlu
2026-06-09 8:10 ` Christian Loehle
2026-06-09 9:40 ` Mete Durlu
2026-06-09 9:52 ` Christian Loehle
2026-06-09 10:04 ` Mete Durlu
2026-06-09 10:39 ` Heiko Carstens
2026-06-09 7:52 ` [PATCH 2/5] tick: Remove arch_needs_cpu Mete Durlu
2026-06-09 15:06 ` Thomas Gleixner
2026-06-09 7:52 ` [PATCH 3/5] s390: Enable TIF_POLLING_NRFLAG Mete Durlu
2026-06-09 7:52 ` [PATCH 4/5] s390/idle: Introduce cpuidle for s390 Mete Durlu
2026-06-09 8:06 ` Christian Loehle
2026-06-09 8:12 ` Christian Loehle [this message]
2026-06-09 9:31 ` Mete Durlu
2026-06-09 10:40 ` Heiko Carstens
2026-06-09 7:52 ` [PATCH 5/5] s390/configs: Enable cpuidle driver on s390 Mete Durlu
2026-06-09 8:06 ` [PATCH 0/5] s390/idle: CPU idle driver Christian Loehle
2026-06-09 8:45 ` Mete Durlu
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=5d9a3d2e-f083-49d4-a311-7801e70ac1a2@arm.com \
--to=christian.loehle@arm.com \
--cc=agordeev@linux.ibm.com \
--cc=anna-maria@linutronix.de \
--cc=borntraeger@linux.ibm.com \
--cc=daniel.lezcano@kernel.org \
--cc=frederic@kernel.org \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®