From: Thomas Gleixner <tglx@kernel.org>
To: Guixin Liu <kanie@linux.alibaba.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Marc Zyngier <maz@kernel.org>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Inochi Amaoto <inochiama@gmail.com>,
Nam Cao <namcao@linutronix.de>,
Shradha Gupta <shradhagupta@linux.microsoft.com>,
Randy Dunlap <rdunlap@infradead.org>
Cc: Xunlei Pang <xlpang@linux.alibaba.com>,
oliver.yang@linux.alibaba.com, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH 2/2] PCI/MSI: Update MSI-X irq domain hwsize
Date: Wed, 25 Mar 2026 14:58:56 +0100 [thread overview]
Message-ID: <87h5q4f1sv.ffs@tglx> (raw)
In-Reply-To: <d57bf449-cd26-4fbd-891e-77534124e997@linux.alibaba.com>
On Wed, Mar 25 2026 at 16:40, Guixin Liu wrote:
> 在 2026/3/25 15:42, Thomas Gleixner 写道:
>> So the straight forward solution is to free the MSI domain when the
>> driver shuts down and tears the MSI interrupts down.
> Yes, I had also considered this aspect before, I will change the scheme
> to this, and send another patch, thanks.
Actually none of that is required. When you update the firmware then
just let the PCI core rescan the device. That makes way more sense as
the new firmware might change other config entries as well not only the
MSI ones.
Thanks,
tglx
next prev parent reply other threads:[~2026-03-25 13:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 1:47 [PATCH 0/2] Update MSI-X irq domain hwsize Guixin Liu
2026-03-24 1:47 ` [PATCH 1/2] genirq/msi: Introduce update hwsize helper Guixin Liu
2026-03-25 8:15 ` Thomas Gleixner
2026-03-25 8:49 ` Guixin Liu
2026-03-24 1:47 ` [PATCH 2/2] PCI/MSI: Update MSI-X irq domain hwsize Guixin Liu
2026-03-24 13:59 ` Thomas Gleixner
2026-03-25 1:34 ` Guixin Liu
2026-03-25 7:42 ` Thomas Gleixner
2026-03-25 8:40 ` Guixin Liu
2026-03-25 13:58 ` Thomas Gleixner [this message]
2026-03-26 1:55 ` Guixin Liu
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=87h5q4f1sv.ffs@tglx \
--to=tglx@kernel.org \
--cc=bhelgaas@google.com \
--cc=inochiama@gmail.com \
--cc=jonathan.cameron@huawei.com \
--cc=kanie@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=maz@kernel.org \
--cc=namcao@linutronix.de \
--cc=oliver.yang@linux.alibaba.com \
--cc=rdunlap@infradead.org \
--cc=shradhagupta@linux.microsoft.com \
--cc=xlpang@linux.alibaba.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