From: Aaron Kling <webgeek1234@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Jonathan Hunter" <jonathanh@nvidia.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Daniel Lezcano" <daniel.lezcano@linaro.org>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v6 3/3] PCI: tegra: Allow building as a module
Date: Thu, 8 May 2025 06:26:39 -0500 [thread overview]
Message-ID: <CALHNRZ8899t0BYMgn1a3iDKz_J9z_Wv_XYM2d8Y4AoiXPZaFjA@mail.gmail.com> (raw)
In-Reply-To: <w2ertcizgmtu27kcike3lpw5dvhvqi2b4c6amqzwdfs2xtebfy@itrpen3oblhs>
On Thu, May 8, 2025 at 3:40 AM Thierry Reding <thierry.reding@gmail.com> wrote:
>
> On Wed, May 07, 2025 at 10:25:54PM -0500, Aaron Kling via B4 Relay wrote:
> > From: Aaron Kling <webgeek1234@gmail.com>
> >
> > This changes the module macro back to builtin, which does not define an
> > exit function. This will prevent the module from being unloaded. There
> > are concerns with modules not cleaning up IRQs on unload, thus this
> > needs specifically disallowed. The remove callback is also dropped as it
> > is unused.
>
> What exactly are these concerns? I haven't done this lately, but I'm
> pretty sure that unbinding the PCI controller is something that I
> extensively tested back when this code was introduced. PCI is designed
> to be hot-pluggable, so there shouldn't be a need to prevent unloading
> of the controller.
>
> Rather than just forcing this to be always there, can we not fix any
> issues and keep this unloadable?
For the short version, see this part of the conversation on v1 [0].
For the long version, read comments on all revisions. Basically, I
originally submitted this as unloadable, but got told that due to
generic concerns that affect all pci drivers, including ones already
modules and unloadable, making this one a module would be blocked if
it was unloadable. Which leads us to this revision of the series.
Sincerely,
Aaron
[0] https://lore.kernel.org/all/4u4h27w77sdjvy43b3yonidhfjuvljylms3qxqfaqwyw3v32qo@kzgrrenxr6yz/
next prev parent reply other threads:[~2025-05-08 11:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 3:25 [PATCH v6 0/3] PCI: tegra: Allow building as a module Aaron Kling via B4 Relay
2025-05-08 3:25 ` [PATCH v6 1/3] irqdomain: Export irq_domain_free_irqs Aaron Kling via B4 Relay
2025-05-08 3:25 ` [PATCH v6 2/3] cpuidle: tegra: Export tegra_cpuidle_pcie_irqs_in_use Aaron Kling via B4 Relay
2025-05-08 3:25 ` [PATCH v6 3/3] PCI: tegra: Allow building as a module Aaron Kling via B4 Relay
2025-05-08 8:40 ` Thierry Reding
2025-05-08 11:26 ` Aaron Kling [this message]
2025-05-28 17:25 ` Aaron Kling
2025-06-13 6:17 ` [PATCH v6 0/3] " Manivannan Sadhasivam
2025-06-30 18:31 ` Aaron Kling
2025-07-14 6:12 ` Aaron Kling
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=CALHNRZ8899t0BYMgn1a3iDKz_J9z_Wv_XYM2d8Y4AoiXPZaFjA@mail.gmail.com \
--to=webgeek1234@gmail.com \
--cc=bhelgaas@google.com \
--cc=daniel.lezcano@linaro.org \
--cc=jonathanh@nvidia.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).