From: Lukas Wunner <lukas@wunner.de>
To: Feng Tang <feng.tang@linux.alibaba.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Jonathan Cameron <Jonthan.Cameron@huawei.com>,
ilpo.jarvinen@linux.intel.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] PCI: Disable PCIE hotplug interrupts early when msi is disabled
Date: Tue, 4 Feb 2025 10:14:10 +0100 [thread overview]
Message-ID: <Z6HaYkIKLXji_EO7@wunner.de> (raw)
In-Reply-To: <20250204053758.6025-2-feng.tang@linux.alibaba.com>
On Tue, Feb 04, 2025 at 01:37:58PM +0800, Feng Tang wrote:
> There was a irq storm bug when testing "pci=nomsi" case, and the root
> cause is: 'nomsi' will disable MSI and let devices and root ports use
> legacy INTX inerrupt, and likely make several devices/ports share one
> interrupt. In the failure case, BIOS doesn't disable the PCIE hotplug
> interrupts, and actually asserts the command-complete interrupt.
> As MSI is disabled, ACPI initialization code will not enumerate root
> port's PCIE hotplug capability, and pciehp service driver wont' be
> enabled for the root port to handle that interrupt, later on when it is
> shared and enabled by other device driver like NVME or NIC, the "nobody
> care irq storm" happens.
>
> So disable the pcie hotplug CCIE/HPIE interrupt in early boot phase when
> MSI is not enbaled.
So I think this issue should go away if disabling the interrupt
by portdrv is no longer conditional on
(pcie_ports_native || host->native_pcie_hotplug)
like I've just proposed here:
https://lore.kernel.org/r/Z6HYuBDP6uvE1Sf4@wunner.de/
... in which case this patch won't be necessary. Can you confirm that?
You can split the change I've proposed into two patches if you like.
Thanks,
Lukas
next prev parent reply other threads:[~2025-02-04 9:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 5:37 [PATCH 1/2] PCI/portdrv: Add necessary delay for disabling hotplug events Feng Tang
2025-02-04 5:37 ` [PATCH 2/2] PCI: Disable PCIE hotplug interrupts early when msi is disabled Feng Tang
2025-02-04 9:14 ` Lukas Wunner [this message]
2025-02-05 6:31 ` Feng Tang
2025-02-05 13:31 ` Feng Tang
2025-02-04 9:23 ` Lukas Wunner
2025-02-05 3:58 ` Feng Tang
2025-02-06 6:21 ` Lukas Wunner
2025-02-12 13:04 ` Feng Tang
2025-02-04 9:07 ` [PATCH 1/2] PCI/portdrv: Add necessary delay for disabling hotplug events Lukas Wunner
2025-02-05 2:46 ` Feng Tang
2025-02-05 17:48 ` Markus Elfring
2025-02-06 2:42 ` Feng Tang
2025-02-06 11:40 ` [1/2] " Markus Elfring
2025-02-07 1:40 ` Feng Tang
2025-02-05 18:26 ` [PATCH 1/2] " Sathyanarayanan Kuppuswamy
2025-02-06 3:18 ` Feng Tang
2025-02-07 4:26 ` Sathyanarayanan Kuppuswamy
2025-02-07 6:17 ` Feng Tang
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=Z6HaYkIKLXji_EO7@wunner.de \
--to=lukas@wunner.de \
--cc=Jonthan.Cameron@huawei.com \
--cc=bhelgaas@google.com \
--cc=feng.tang@linux.alibaba.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.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