From: Thomas Gleixner <tglx@kernel.org>
To: Herve Codina <herve.codina@bootlin.com>,
Qingshuang Fu <fuqingshuang@kylinos.cn>
Cc: Radu Rendec <radu@rendec.net>, Andy Whitcroft <apw@canonical.com>,
Joe Perches <joe@perches.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] genirq/generic-chip: Set IRQ_DOMAIN_FLAG_DESTROY_GC in irq_domain_alloc_generic_chips()
Date: Fri, 04 Sep 2026 08:26:26 +0200 [thread overview]
Message-ID: <87v78l8rcd.ffs@fw13> (raw)
In-Reply-To: <20260904003731.2fed5a25@bootlin.com>
On Fri, Sep 04 2026 at 00:37, Herve Codina wrote:
> On Wed, 2 Sep 2026 14:59:39 +0800
> Qingshuang Fu <fuqingshuang@kylinos.cn> wrote:
>> diff --git a/kernel/irq/generic-chip.c b/kernel/irq/generic-chip.c
>> index 2c8bc6ce082e..13b634053a3e 100644
>> --- a/kernel/irq/generic-chip.c
>> +++ b/kernel/irq/generic-chip.c
>> @@ -308,6 +308,7 @@ int irq_domain_alloc_generic_chips(struct irq_domain *d,
>> dgc->gc_flags = info->gc_flags;
>> dgc->exit = info->exit;
>> d->gc = dgc;
>> + d->flags |= IRQ_DOMAIN_FLAG_DESTROY_GC;
>>
>> /* Calc pointer to the first generic chip */
>> tmp += dgc_sz;
> The flag has been intended to be use with irq_domain_instantiate() which can call
> irq_domain_alloc_generic_chips() internally. Callers of irq_domain_instantiate()
> call only irq_remove_domain().
>
> Indeed calling only irq_domain_instantiate() and calling both
> irq_domain_remove_generic_chips() followed by irq_remove_domain() is, in that case,
> not consistent too.
>
> IHMO, if the flag IRQ_DOMAIN_FLAG_DESTROY_GC need to be automatically set
> somewhere, it could be in irq_domain_instantiate().
Yes, in the 'if (info->dgc_info)' branch.
next prev parent reply other threads:[~2026-09-04 6:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 6:59 Qingshuang Fu
2026-09-03 22:37 ` Herve Codina
2026-09-04 6:26 ` Thomas Gleixner [this message]
2026-09-04 7:25 ` Qingshuang Fu
2026-09-04 7:09 ` [PATCH v2] irqdomain: Auto-set IRQ_DOMAIN_FLAG_DESTROY_GC in __irq_domain_instantiate() Qingshuang Fu
2026-09-04 11:09 ` Herve Codina
2026-09-04 15:19 ` Thomas Gleixner
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=87v78l8rcd.ffs@fw13 \
--to=tglx@kernel.org \
--cc=apw@canonical.com \
--cc=fuqingshuang@kylinos.cn \
--cc=herve.codina@bootlin.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=radu@rendec.net \
/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®