From: Bjorn Helgaas <helgaas@kernel.org>
To: Maverickk 78 <maverickk1778@gmail.com>
Cc: Keith Busch <kbusch@kernel.org>, linux-pci@vger.kernel.org
Subject: Re: pcie hotplug driver probe is not getting called
Date: Fri, 4 Oct 2024 16:56:57 -0500 [thread overview]
Message-ID: <20241004215657.GA362992@bhelgaas> (raw)
In-Reply-To: <CALfBBTuhUcdBAQgKFhGP+9gMqEthA_dOE6V3RGn6HTZm7nNBYg@mail.gmail.com>
On Fri, Oct 04, 2024 at 11:50:28PM +0530, Maverickk 78 wrote:
> The platform I am working on is rtl simulation of pcie switch(Gen6)
> with a backdoor mechanism to trigger the HotPlug event.
>
> Tried following patches independently to have both hotplug and dpc
> driver register and handle respective events.
>
> https://patchwork.ozlabs.org/project/linux-pci/patch/20231223212235.34293-2-mattc@purestorage.com/
> https://patchwork.kernel.org/project/linux-pci/patch/20240108194642.30460-1-mattc@purestorage.com/#25680870
>
> Tried following
>
> - Trigger hot removal and add, the event is triggered and respective
> msi in /proc/interrupt increments and kernel logs the event(dmesg)
> - Trigger hot removal and add, the event is triggered and respective
> msi in /proc/interrupt increments and kernel logs the event(dmesg)
> - Trigger DPC using "DPC software trigger" in DPC control register
>
> The kernel hangs, the console is non-responsive.
>
> Can dpc and pciehp co-exist and handle the events?
Yes, they're intended to coexist. Your platform firmware doesn't
advertise support for it, though:
[ 1.736168] acpi PNP0A08:00: _OSC: platform does not support [PCIeHotplug LTR DPC]
I don't think there's a kernel parameter to force DPC usage if the
platform doesn't advertise it. There should be a message like "DPC:
enabled with IRQ X" if the dpc driver is active.
Even if the dpc driver isn't active, I don't think the kernel should
hang if you trigger DPC. Since this is a QEMU guest, you should be
able to use a debugger to figure out why it's hung.
Bjorn
next prev parent reply other threads:[~2024-10-04 21:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 15:20 pcie hotplug driver probe is not getting called Maverickk 78
2024-09-27 17:17 ` Bjorn Helgaas
2024-09-29 13:59 ` Maverickk 78
2024-09-30 12:49 ` Maverickk 78
2024-09-30 19:28 ` Bjorn Helgaas
2024-10-01 12:48 ` Maverickk 78
2024-10-01 18:09 ` Maverickk 78
2024-10-01 18:19 ` Keith Busch
[not found] ` <CALfBBTtxJB1BQkSZ=RBKCiZKNeTxsJHAZ50jdBUjNSmOf79NWw@mail.gmail.com>
2024-10-04 18:20 ` Maverickk 78
2024-10-04 21:56 ` Bjorn Helgaas [this message]
[not found] ` <CALfBBTtjXJiZBSfFTUAPsD+G15nPQQsn-2sCrAt1UwPsrNsqNg@mail.gmail.com>
2024-10-15 8:44 ` Maverickk 78
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=20241004215657.GA362992@bhelgaas \
--to=helgaas@kernel.org \
--cc=kbusch@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=maverickk1778@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).