From: Thomas Gleixner <tglx@kernel.org>
To: Tianyang Zhang <zhangtianyang@loongson.cn>,
chenhuacai@kernel.org, kernel@xen0n.name, corbet@lwn.net,
alexs@kernel.org, si.yanteng@linux.dev, jiaxun.yang@flygoat.com,
maobibo@loongson.cn
Cc: loongarch@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Tianyang Zhang <zhangtianyang@loongson.cn>
Subject: Re: [PATCH v9 3/4] irqchip/loongarch-avec.c:return IRQ_SET_MASK_OK_DONE when keep affinity
Date: Fri, 30 Jan 2026 09:20:31 +0100 [thread overview]
Message-ID: <87343nmrzk.ffs@tglx> (raw)
In-Reply-To: <20260130025941.2140582-4-zhangtianyang@loongson.cn>
On Fri, Jan 30 2026 at 10:59, Tianyang Zhang wrote:
irqchip/irq-loonarch-avec: Return IRQ_SET_MASK_OK_DONE when affinity is unchanged
Note the space between 'prefix: ' and the shortlog sentence
> When it is detected in avecintc_set_affinity that the current affinity
Functions are denoted with fname() to make it clear. See
https://www.kernel.org/doc/html/latest/process/maintainer-tip.html#patch-submission-notes
> remains valid, the return value is modified to IRQ_SET_MASK_OK_DONE.
That's the very wrong order of explaining the change. You again explain
the _what_ first without giving context and reason.
See the above link. It provides guidance about structuring a change log.
> After the introduction of redirect-domain, for each interrupt source,
> avecintc-domain only provides the CPU/interrupt vector, while redirect-domain
> provides other operations to synchronize interrupt affinity information
> among multiple cores. The original intention is to notify the cascaded
> redirect_set_affinity that multi-core synchronization is not required.
"After the introduction.." is confusing at best.
> However, this introduces some compatibility issues, such as the new return
> value causing msi_domain_set_affinity to no longer perform irq_chip_write_msi_msg.
> 1) When redirect exist in the system, the msi msg_address and msg_data no
> longer changes after the allocation phase, so it does not actually require updating
> the MSI message info.
> 2) When only avecintc exists in the system, the irq_domain_activate_irq
> interface will be responsible for the initial configuration of the MSI message,
> which is unconditional. After that, if unnecessary, no modification to the MSI
> message is alse correctly.
Spell checkers exist for a reason.
Thanks
tglx
next prev parent reply other threads:[~2026-01-30 8:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 2:59 [PATCH v9 0/4] Loongarch irq-redirect support Tianyang Zhang
2026-01-30 2:59 ` [PATCH v9 1/4] Docs/LoongArch: Add Advanced Extended-Redirect IRQ model description Tianyang Zhang
2026-01-30 2:59 ` [PATCH v9 2/4] irqchip/irq-loongson.h:irq-loongson.h preparation for Redirect irqchip Tianyang Zhang
2026-01-30 8:14 ` Thomas Gleixner
2026-01-30 2:59 ` [PATCH v9 3/4] irqchip/loongarch-avec.c:return IRQ_SET_MASK_OK_DONE when keep affinity Tianyang Zhang
2026-01-30 8:20 ` Thomas Gleixner [this message]
2026-01-30 9:05 ` Tianyang Zhang
2026-01-30 2:59 ` [PATCH v9 4/4] irqchip/irq-loongarch-ir:Add Redirect irqchip support Tianyang Zhang
2026-01-30 8:33 ` kernel test robot
2026-01-30 8:54 ` Thomas Gleixner
2026-02-02 1:00 ` Tianyang Zhang
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=87343nmrzk.ffs@tglx \
--to=tglx@kernel.org \
--cc=alexs@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=corbet@lwn.net \
--cc=jiaxun.yang@flygoat.com \
--cc=kernel@xen0n.name \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=maobibo@loongson.cn \
--cc=si.yanteng@linux.dev \
--cc=zhangtianyang@loongson.cn \
/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