summaryrefslogtreecommitdiffstats
path: root/rust
diff options
context:
space:
mode:
authorNikola Prica <nikola.prica@amd.com>2026-09-21 13:19:03 +0200
committerBjorn Helgaas <bhelgaas@google.com>2026-10-02 11:21:28 -0500
commit40cce45b921f7930886bcba43069edc579725457 (patch)
treeb4c55916d7e55b570bd010b5690847ae84719e07 /rust
parentcee9395acd8043be0644b25c34bfa86623f2b935 (diff)
downloadlinux-stable-40cce45b921f7930886bcba43069edc579725457.tar.gz
linux-stable-40cce45b921f7930886bcba43069edc579725457.zip
PCI: Accept AtomicOps already enabled by the hypervisor
pci_enable_atomic_ops_to_root() currently fails when no Root Port is visible. That is common in passthrough guests (ESXi, Hyper-V): the Endpoint is assigned to the VM, but the Root Port above it is not visible in the guest topology. In those setups the hypervisor may already have enabled AtomicOp Requester Enable on the device. If PCI_EXP_DEVCTL2_ATOMIC_REQ is set, treat AtomicOps as already enabled and return success instead of failing the Root Port walk. After 1ae8c4ce1570 ("PCI: Enable AtomicOps only if Root Port supports them"), pci_enable_atomic_ops_to_root() always returns failure if the Root Port is not visible, so drivers don't use atomics when they could. On systems where the Root Port is not visible but *does* support AtomicOps, this is a regression: prior to 1ae8c4ce1570, it enabled AtomicOps in the endpoint and returned success. Fixes: 1ae8c4ce1570 ("PCI: Enable AtomicOps only if Root Port supports them") Signed-off-by: Nikola Prica <nikola.prica@amd.com> [bhelgaas: commit log, code comment] Signed-off-by: Bjorn Helgaas <bhelgaas@google.com> Tested-by: Gerd Bayer <gbayer@linux.ibm.com> Reviewed-by: Christian König <christian.koenig@amd.com> Reviewed-by: Gerd Bayer <gbayer@linux.ibm.com> Link: https://patch.msgid.link/20260921111903.978687-1-nikprica@amd.com
Diffstat (limited to 'rust')
0 files changed, 0 insertions, 0 deletions