From: Thomas Gleixner <tglx@kernel.org>
To: Qiliang Yuan <realwujing@gmail.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <neeraj.upadhyay@kernel.org>,
Joel Fernandes <joelagnelf@nvidia.com>,
Josh Triplett <josh@joshtriplett.org>,
Boqun Feng <boqun.feng@gmail.com>,
Uladzislau Rezki <urezki@gmail.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Zqiang <qiang.zhang@linux.dev>, Tejun Heo <tj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
Brendan Jackman <jackmanb@google.com>,
Johannes Weiner <hannes@cmpxchg.org>, Zi Yan <ziy@nvidia.com>,
Anna-Maria Behnsen <anna-maria@linutronix.de>,
Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org, rcu@vger.kernel.org,
linux-mm@kvack.org, Qiliang Yuan <realwujing@gmail.com>,
Qiliang Yuan <yuanql9@chinatelecom.cn>
Subject: Re: [PATCH RFC 03/12] genirq: Implement dynamic migration for Managed IRQs
Date: Fri, 06 Feb 2026 13:24:25 +0100 [thread overview]
Message-ID: <871piy12me.ffs@tglx> (raw)
In-Reply-To: <20260206-feature-dynamic_isolcpus_dhei-v1-3-00a711eb0c74@gmail.com>
On Fri, Feb 06 2026 at 02:04, Qiliang Yuan wrote:
s/Managed IRQs/managed interrupts/ in $subject
> Support dynamic reconfiguration of CPU isolation by making the managed
> interrupts responsive to housekeeping mask changes at runtime.
>
> 1. Register a housekeeping notifier in the genirq subsystem to listen
> for HK_TYPE_MANAGED_IRQ updates.
> 2. Iterate through all active interrupts when a mask update occurs.
> 3. Re-apply affinity for managed interrupts to ensure they honor the
> newly configured housekeeping mask.
> 4. Use irq_set_affinity_locked() to trigger migration away from newly
> isolated CPUs or towards newly designated housekeeping CPUs.
Please don't explain implementation details in the change log. They can
be seen from the patch. Explain the why and the concept of the change
https://www.kernel.org/doc/html/latest/process/maintainer-tip.html#changelog
> Signed-off-by: Qiliang Yuan <realwujing@gmail.com>
> Signed-off-by: Qiliang Yuan <yuanql9@chinatelecom.cn>
So you developed that together with your alter ego? Pick one please.
> +#ifdef CONFIG_SMP
> +static int irq_housekeeping_reconfigure(struct notifier_block *nb,
> + unsigned long action, void *data)
> +{
> + struct housekeeping_update *upd = data;
> + struct irq_desc *desc;
Move desc into the loop
> + unsigned int irq;
> +
> + if (action != HK_UPDATE_MASK || upd->type != HK_TYPE_MANAGED_IRQ)
> + return NOTIFY_OK;
> +
> + irq_lock_sparse();
> + for_each_active_irq(irq) {
> + struct irq_data *id;
id is really not a intuitive name. Most code here uses 'irqd'.
> + desc = irq_to_desc(irq);
> + if (!desc)
> + continue;
> +
> + scoped_guard(raw_spinlock_irqsave, &desc->lock) {
raw_spinlock_irq. There is nothing to save here as this is preemptible
thread context, no?
You can simplify all of the above by using:
scoped_irqdesc_get_and_lock(irq, 0) {
struct irq_data *irqd = irq_desc_get_irq_data(scoped_irqdesc);
....
> + id = irq_desc_get_irq_data(desc);
> + if (!irqd_affinity_is_managed(id) || !desc->action ||
> + !irq_data_get_irq_chip(id))
No line break required. You have 100 characters.
> + continue;
Thanks,
tglx
next prev parent reply other threads:[~2026-02-06 12:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 7:04 [PATCH RFC 00/12] Implementation of Dynamic Housekeeping & Enhanced Isolation (DHEI) Qiliang Yuan
2026-02-06 7:04 ` [PATCH RFC 01/12] sched/isolation: Remove __init restriction from housekeeping cores Qiliang Yuan
2026-02-06 7:04 ` [PATCH RFC 02/12] sched/isolation: Introduce reconfiguration notifier chain Qiliang Yuan
2026-02-06 7:04 ` [PATCH RFC 03/12] genirq: Implement dynamic migration for Managed IRQs Qiliang Yuan
2026-02-06 12:24 ` Thomas Gleixner [this message]
2026-02-06 7:04 ` [PATCH RFC 04/12] rcu: Sync RCU housekeeping mask on notification Qiliang Yuan
2026-02-06 7:04 ` [PATCH RFC 05/12] sched/core: Dynamic update housekeeping_cpumask(HK_TYPE_DOMAIN) Qiliang Yuan
2026-02-06 7:04 ` [PATCH RFC 06/12] watchdog: Allow runtime toggle of hardlockup detector on CPUs Qiliang Yuan
2026-02-06 7:04 ` [PATCH RFC 07/12] workqueue: Dynamic housekeeping mask update support Qiliang Yuan
2026-02-06 7:04 ` [PATCH RFC 08/12] kcompactd: Add housekeeping notifier for dynamic mask update Qiliang Yuan
2026-02-06 15:09 ` Zi Yan
2026-02-06 7:04 ` [PATCH RFC 09/12] sched/isolation: Separate housekeeping types and add sysfs interface Qiliang Yuan
2026-02-06 7:04 ` [PATCH RFC 10/12] tick/nohz: Implement dynamic nohz_full state update Qiliang Yuan
2026-02-06 7:04 ` [PATCH RFC 11/12] sched/isolation: Implement SMT sibling auto-isolation and safety check Qiliang Yuan
2026-02-06 7:04 ` [PATCH RFC 12/12] sched/isolation: Bridge isolcpus and support runtime tick offload init Qiliang Yuan
2026-02-20 19:07 ` [PATCH RFC 00/12] Implementation of Dynamic Housekeeping & Enhanced Isolation (DHEI) Joel Fernandes
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=871piy12me.ffs@tglx \
--to=tglx@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anna-maria@linutronix.de \
--cc=boqun.feng@gmail.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=frederic@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=jackmanb@google.com \
--cc=jiangshanlai@gmail.com \
--cc=joelagnelf@nvidia.com \
--cc=josh@joshtriplett.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mgorman@suse.de \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=qiang.zhang@linux.dev \
--cc=rcu@vger.kernel.org \
--cc=realwujing@gmail.com \
--cc=rostedt@goodmis.org \
--cc=surenb@google.com \
--cc=tj@kernel.org \
--cc=urezki@gmail.com \
--cc=vbabka@suse.cz \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=yuanql9@chinatelecom.cn \
--cc=ziy@nvidia.com \
/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