Linux PCI subsystem development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Yury Murashka" <yurypm@arista.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH v3 2/2] PCI: Add pci=nodpc kernel boot option
Date: Thu, 22 Oct 2026 17:03:37 +0000	[thread overview]
Message-ID: <sashiko-outbox-181844@kernel.org> (raw)
In-Reply-To: <20261022165842.1463451-3-yurypm@arista.com>

> Add pci=nodpc to let Linux opt out of Downstream Port Containment (DPC)
> and Error Disconnect Recover (EDR) support on systems where userspace
> manages PCIe errors.
> 
> Skip DPC initialization, state operations, hotplug recovery checks, and
> port service registration when disabled. Expose pci_dpc_available() so
> ACPI negotiation and PCIe port service discovery honor the same policy.
> Do not advertise EDR support or request DPC control through _OSC, and
> prevent native-port overrides from reintroducing DPC ownership.
> 
> Skip EDR notifier installation before the DPC-enabling _DSM call. Merely
> skipping the native DPC driver would allow EDR to enable hardware DPC
> while the handler lacks the capability information needed to recover.
> 
> The option disables Linux participation in DPC and EDR; it does not turn
> off firmware-owned DPC hardware. AER reporting and recovery remain
> independent and can be controlled with their own boot options.
> 
> Signed-off-by: Yury Murashka <yurypm@arista.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261022165842.1463451-1-yurypm@arista.com?part=2


      reply	other threads:[~2026-10-22 17:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-22 16:58 [PATCH v3 0/2] PCI: Add boot options to disable DPC and AER recovery Yury Murashka
2026-10-22 16:58 ` [PATCH v3 1/2] PCI: Add pci=noaer_recovery kernel boot option Yury Murashka
2026-10-22 17:03   ` sashiko-bot
2026-10-22 16:58 ` [PATCH v3 2/2] PCI: Add pci=nodpc " Yury Murashka
2026-10-22 17:03   ` sashiko-bot [this message]

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=sashiko-outbox-181844@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=yurypm@arista.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