From: Marc Zyngier <maz@kernel.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Fate of CONFIG_IRQ_TIMINGS and co
Date: Sat, 06 Dec 2025 10:12:22 +0000 [thread overview]
Message-ID: <87zf7vex6h.wl-maz@kernel.org> (raw)
Hi both,
While fixing some ancient MIPS crap, I noticed that the IRQF_TIMER
flag wasn't being provided to any clockevent driver that uses percpu
interrupts, starting with the ARM architected timer.
Thinking that I might as well be fixing that, I started to dig into
it, only to realise that it is simply impossible to enable the IRQ
timing subsystem (CONFIG_IRQ_TIMINGS isn't selectable by a luser, and
TEST_IRQ_TIMINGS depends on it...).
Even if I manually hack the Kconfig to compile the timing
infrastructure and allow the selftest to be selected, nothing really
makes use of this, as the static key that controls the accounting is
never flipped. The selftest itself only cares about the accounting
data structure, and not interrupts.
This appears to be dead code, and seems to have been so for the past 6
years.
The obvious question is therefore: why do we have it the first place?
It isn't finished, not plugged in, and if it was, would fail to
correctly account for exactly 100% of the timer interrupts on the
systems I care about.
If this is a work in progress and that there is a line of sight to
having it working upstream, that's great, and I will happily post the
few fixes I have for it. Otherwise, can we do ourselves a favour and
consider dropping it?
Thanks,
M.
--
Jazz isn't dead. It just smells funny.
next reply other threads:[~2025-12-06 10:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-06 10:12 Marc Zyngier [this message]
2025-12-08 4:49 ` Fate of CONFIG_IRQ_TIMINGS and co Daniel Lezcano
2025-12-10 1:13 ` Thomas Gleixner
2025-12-10 4:47 ` Daniel Lezcano
2025-12-10 8:25 ` Marc Zyngier
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=87zf7vex6h.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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