From: Jinjie Ruan <ruanjinjie@huawei.com>
To: Marc Zyngier <maz@kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-mips@vger.kernel.org>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Joshua Kinard <kumba@gentoo.org>
Subject: Re: [PATCH 1/6] genirq: Remove IRQ timing tracking infrastructure
Date: Thu, 11 Dec 2025 09:32:39 +0800 [thread overview]
Message-ID: <7d0e0ce8-91da-0fd4-e509-27961388af60@huawei.com> (raw)
In-Reply-To: <20251210082242.360936-2-maz@kernel.org>
On 2025/12/10 16:22, Marc Zyngier wrote:
> The IRQ timing tracking infrastructure was merged in 2019, but was
> never plumbed in, is not selectable, and is therefore never used.
>
> As Daniel agrees that there is little hope for this infrastructure
> to be completed in the near term, drop it altogether.
>
> Signed-off-by: Marc Zyngier <maz@kernel.org>
> Link: https://lore.kernel.org/r/87zf7vex6h.wl-maz@kernel.org
> ---
> include/linux/interrupt.h | 6 -
> kernel/irq/Kconfig | 3 -
> kernel/irq/Makefile | 4 -
> kernel/irq/handle.c | 2 -
> kernel/irq/internals.h | 110 -----
> kernel/irq/manage.c | 3 -
> kernel/irq/timings.c | 959 --------------------------------------
> lib/Kconfig.debug | 8 -
> 8 files changed, 1095 deletions(-)
> delete mode 100644 kernel/irq/timings.c
Reviewed-by: Jinjie Ruan <ruanjinjie@huawei.com>
>
> diff --git a/include/linux/interrupt.h b/include/linux/interrupt.h
> index 266f2b39213a0..44e335b17ed64 100644
> --- a/include/linux/interrupt.h
> +++ b/include/linux/interrupt.h
> @@ -871,12 +871,6 @@ static inline void init_irq_proc(void)
> }
> #endif
>
> -#ifdef CONFIG_IRQ_TIMINGS
> -void irq_timings_enable(void);
> -void irq_timings_disable(void);
> -u64 irq_timings_next_event(u64 now);
> -#endif
> -
[...]
> -
> config TEST_LKM
> tristate "Test module loading with 'hello world' module"
> depends on m
next prev parent reply other threads:[~2025-12-11 1:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 8:22 [PATCH 0/6] genirq: Post 6.19-rc1 API cleanup Marc Zyngier
2025-12-10 8:22 ` [PATCH 1/6] genirq: Remove IRQ timing tracking infrastructure Marc Zyngier
2025-12-11 1:32 ` Jinjie Ruan [this message]
2025-12-15 21:27 ` [tip: irq/core] " tip-bot2 for Marc Zyngier
2025-12-10 8:22 ` [PATCH 2/6] genirq: Remove __request_percpu_irq() helper Marc Zyngier
2025-12-11 1:46 ` Jinjie Ruan
2025-12-15 21:27 ` [tip: irq/core] " tip-bot2 for Marc Zyngier
2025-12-10 8:22 ` [PATCH 3/6] mips: Move IP30 timer to request_percpu_irq() Marc Zyngier
2025-12-11 1:58 ` Jinjie Ruan
2025-12-11 8:20 ` Marc Zyngier
2025-12-15 21:27 ` [tip: irq/core] MIPS: " tip-bot2 for Marc Zyngier
2025-12-10 8:22 ` [PATCH 4/6] mips: Move IP27 " Marc Zyngier
2025-12-15 21:27 ` [tip: irq/core] MIPS: " tip-bot2 for Marc Zyngier
2025-12-10 8:22 ` [PATCH 5/6] clocksource: mips-gic-timer: Move GIC " Marc Zyngier
2025-12-15 21:27 ` [tip: irq/core] clocksource/drivers/mips-gic-timer: " tip-bot2 for Marc Zyngier
2026-01-29 21:32 ` [tip: timers/clocksource] " tip-bot2 for Marc Zyngier
2025-12-10 8:22 ` [PATCH 6/6] genirq: Kill setup_percpu_irq() Marc Zyngier
2025-12-15 21:27 ` [tip: irq/core] genirq: Remove setup_percpu_irq() tip-bot2 for 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=7d0e0ce8-91da-0fd4-e509-27961388af60@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=daniel.lezcano@linaro.org \
--cc=kumba@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=maz@kernel.org \
--cc=tglx@linutronix.de \
--cc=tsbogend@alpha.franken.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
all inboxes | Powered by JetHome®