Page MenuHomeFreeBSD

acpi_pci: Honor device proximity for DMA tags
ClosedPublic

Authored by kbowling on Aug 21 2026, 3:52 AM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Oct 12, 11:14 PM
Unknown Object (File)
Tue, Oct 6, 6:55 PM
Unknown Object (File)
Tue, Oct 6, 5:31 PM
Unknown Object (File)
Mon, Oct 5, 10:26 PM
Unknown Object (File)
Mon, Oct 5, 9:23 AM
Unknown Object (File)
Mon, Oct 5, 9:00 AM
Unknown Object (File)
Sun, Oct 4, 7:05 PM
Unknown Object (File)
Sun, Oct 4, 1:03 AM
Subscribers

Details

Summary
A PCI function with its own _PXM still inherits a DMA tag carrying
the upstream bridge's proximity domain. Resolving an SR-IOV VF's
locality through its PF therefore does not affect the domain used for
DMA allocations.

Create and cache a private child tag when the function, or a VF's
owning PF, has an explicit _PXM. Parent it to the existing PCI or IOMMU
tag so its constraints remain intact, then apply the function's domain
without mutating a shared tag.

pci_get_dma_tag() already performs the IOMMU lookup, so remove the
duplicated lookup in the ACPI subclass while here.

MFC after:      2 weeks

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

I would maybe split out the caching of the domain into a separate commit.

sys/dev/acpica/acpi_pci.c
571

s/root/parent/?

This revision is now accepted and ready to land.Aug 27 2026, 1:58 PM