From: Heiko Carstens <hca@linux.ibm.com>
To: Mete Durlu <meted@linux.ibm.com>
Cc: Christian Loehle <christian.loehle@arm.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>,
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 1/5] s390/tick: Remove CIF_NOHZ_DELAY flag
Date: Tue, 9 Jun 2026 12:39:04 +0200 [thread overview]
Message-ID: <20260609103904.9217Afa-hca@linux.ibm.com> (raw)
In-Reply-To: <b2b8cf98-bc41-43b6-838b-60822a9a4c89@linux.ibm.com>
On Tue, Jun 09, 2026 at 12:04:08PM +0200, Mete Durlu wrote:
> On 6/9/26 11:52, Christian Loehle wrote:
> > > > > Remove obsolete tick delay heuristic [1]. The upcoming cpuidle driver
> > > > > handles frequent sleep/wakeup cycles more effectively.
> > > > >
> > > > > [1] https://lore.kernel.org/all/20090929122533.402715150@de.ibm.com/
> > > > >
> > > > > Suggested-by: Heiko Carstens <hca@linux.ibm.com>
> > > > > Signed-off-by: Mete Durlu <meted@linux.ibm.com>
> > > > > ---
> > > > For bisectibility does it make sense to move this and 2/5 to the end?
> > >
> > > I am unable to see how that would help. Could you elaborate?
> >
> > CIF_NOHZ_DELAY is only obsolete because of the new s390 cpuidle driver
> > handles NOHZ better overall right?
> > So my suggestion was to only obsolete it once everything is in place?
>
> CIF_NOHZ_DELAY could modify the idle driver's decisions when it comes to
> disabling the scheduling tick. It could be hard to bisect a problem with
> the driver if we move the removal of the flag after the drivers
> introduction. Because then the commit that enables the driver can have
> a significantly different behavior.
>
> Plus,having the flag obsolete without any other mechanism doing a
> similar job would make the effect and related behavior more visible and
> easier to debug.
The flag is questionable since a long time. So I wouldn't focus on the
question if the removal comes at the beginning or end of this series.
I'm more than happy to see it go.
next prev parent reply other threads:[~2026-06-09 10:39 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 [this message]
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
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=20260609103904.9217Afa-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-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