From: Qiliang Yuan <realwujing@gmail.com>
To: Thomas Gleixner <tglx@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 02,04,05/12] DHM: Dynamic Housekeeping Management
Date: Mon, 20 Apr 2026 17:20:59 +0800 [thread overview]
Message-ID: <20260420092059.240701-1-realwujing@gmail.com> (raw)
In-Reply-To: <20260414212543.123456-1-tglx@kernel.org>
Point taken regarding the notifier ordering and complexity. For v3, I will
replace the generic notifier chain in genirq and tick subsystems with
explicit, controlled function calls to ensure deterministic execution.
> Why is this exported? Are random modules allowed to invoke this?
The export of tick_nohz_full_mask in Patch 02 will be removed. I'll implement
a restricted helper instead to prevent unintended usage by modules.
On Tue, 14 Apr 2026 23:57:52 +0200, Thomas Gleixner wrote:
> I have no idea what DHEI is. Provide proper information and not magic
> acronyms.
Documentation will be updated to replace "DHEI" with standard kernel
nomenclature.
> Refactoring has to be done in a preparatory patch and not in the middle
> of a feature.
I will reorganize the series by moving the necessary infrastructure changes
into preparatory patches.
> next_timer? Please pick variable names which are comprehensible and self
> explaining. Also why can't you re-use timer_cpu, which would be actually
> useful?
Variable naming will be adjusted for better clarity, and I will explore
re-using timer_cpu as suggested.
> That's not sufficient. Assume an interrupt was shut down before the
> change because there was no online CPU in the affinity mask, but now the
> affinity mask changes so there is an online CPU. What starts it up?
> Same the other way around.
The managed IRQ migration logic will be revised to correctly track and
re-evaluate the interrupt state across affinity changes.
Best regards,
Qiliang
---
To: Frederic Weisbecker <frederic@kernel.org>
Subject: Re: [PATCH v2 01,03,07,08,09/12] DHM Architecture and Cpuset Integration
Date: Mon, 20 Apr 2026 16:10:00 +0800
Hi Frederic,
On Wed, 15 Apr 2026 12:02:46 +0200, Frederic Weisbecker wrote:
parent reply other threads:[~2026-04-20 9:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260414212543.123456-1-tglx@kernel.org>]
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=20260420092059.240701-1-realwujing@gmail.com \
--to=realwujing@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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