From: Darshit Shah <darnshah@amazon.de>
To: <lukas@wunner.de>
Cc: <Jonthan.Cameron@huawei.com>, <bhelgaas@google.com>,
<darnir@gnu.org>, <darnshah@amazon.de>,
<feng.tang@linux.alibaba.com>, <kwilczynski@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-pci@vger.kernel.org>,
<nh-open-source@amazon.com>,
<sathyanarayanan.kuppuswamy@linux.intel.com>
Subject: [PATCH v2 1/1] drivers/pci: Decouple DPC from AER service
Date: Mon, 8 Dec 2025 11:25:45 +0000 [thread overview]
Message-ID: <20251208112545.21315-2-darnshah@amazon.de> (raw)
In-Reply-To: <20251208112545.21315-1-darnshah@amazon.de>
According to [1] it is recommended that the Operating System link the
enablement of Downstream Port Containment (DPC) to the enablement of
Advanced Error Reporting (AER).
However, AER is advertised only on Root Port (RP) or Root Complex Event
Collector (RCEC) devices. On the other hand, DPC may be advertised on
any PCIe device in the hierarchy. In fact, since the main usecase of DPC
is for the switch upstream of an endpoint device to trigger a signal to
the host-bridge, it is imperative that it be supported on non-RP,
non-RCEC devices.
Previously portdrv has interpreted [1] to mean that the AER service must
be available on the same device in order for DPC to be available. This is
not what the implementation note in [1] meant to imply. If the firmware
hands the OS control of AER via _OSC on the host bridge upstream of the
device, then the OS should be allowed to assume control of DPC on that device.
The comment above this check alludes to this, by saying:
> With dpc-native, allow Linux to use DPC even if it doesn't have permission
> to use AER.
However, permission to use AER is negotiated at the host bridge, not
per-device. So we should not link DPC to enabling AER at the device.
Instead, DPC should be enabled if the OS has control of AER for the
host bridge that is upstream of the device in question, or if dpc-native
was set on the command line.
[1]: PCI Express Base Specification Revision 5.0 Version 1.0, Sec. 6.2.10
Signed-off-by: Darshit Shah <darnshah@amazon.de>
---
Changes in patch v2:
* Don't touch the PCIE_PORT_SERVICE_AER attachment
* Stop relying on PCIE_PORT_SERVICE_AER for enabling DPC
* Instead test that OS has control of AER at parent host bridge
drivers/pci/pcie/portdrv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pci/pcie/portdrv.c b/drivers/pci/pcie/portdrv.c
index 38a41ccf79b9..8db2fa140ae2 100644
--- a/drivers/pci/pcie/portdrv.c
+++ b/drivers/pci/pcie/portdrv.c
@@ -264,7 +264,7 @@ static int get_port_device_capability(struct pci_dev *dev)
*/
if (pci_find_ext_capability(dev, PCI_EXT_CAP_ID_DPC) &&
pci_aer_available() &&
- (pcie_ports_dpc_native || (services & PCIE_PORT_SERVICE_AER)))
+ (host->native_aer || pcie_ports_dpc_native))
services |= PCIE_PORT_SERVICE_DPC;
/* Enable bandwidth control if more than one speed is supported. */
--
2.47.3
Amazon Web Services Development Center Germany GmbH
Tamara-Danz-Str. 13
10243 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Christof Hellmis
Eingetragen am Amtsgericht Charlottenburg unter HRB 257764 B
Sitz: Berlin
Ust-ID: DE 365 538 597
next prev parent reply other threads:[~2025-12-08 11:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 12:20 [PATCH] drivers/pci: Allow attaching AER to non-RP devices that support MSI Darshit Shah
2025-11-28 17:07 ` Lukas Wunner
2025-12-08 11:25 ` [PATCH v2 0/1] " Darshit Shah
2025-12-08 11:25 ` Darshit Shah [this message]
2025-12-09 7:45 ` [PATCH v2 1/1] drivers/pci: Decouple DPC from AER service Lukas Wunner
2025-12-11 16:42 ` [PATCH v3] " Darshit Shah
2026-02-28 23:59 ` Darshit Shah
2025-12-09 15:29 ` [PATCH v2 1/1] " Sathyanarayanan Kuppuswamy
2025-12-09 0:30 ` [PATCH] drivers/pci: Allow attaching AER to non-RP devices that support MSI Bjorn Helgaas
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=20251208112545.21315-2-darnshah@amazon.de \
--to=darnshah@amazon.de \
--cc=Jonthan.Cameron@huawei.com \
--cc=bhelgaas@google.com \
--cc=darnir@gnu.org \
--cc=feng.tang@linux.alibaba.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=nh-open-source@amazon.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.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