On 2025/3/12 18:10, Robin Murphy wrote:
On 2025-03-11 6:42 pm, Joerg Roedel wrote:
Hi Robin,
On Fri, Feb 28, 2025 at 03:46:33PM +0000, Robin Murphy wrote:
+ /*
+ * And if we do now see any replay calls, they would indicate
someone
+ * misusing the dma_configure path outside bus code.
+ */
+ if (dev->driver)
+ dev_WARN(dev, "late IOMMU probe at driver bind, something
fishy here!\n");
This warning triggers on my workstation (with an AMD IOMMU), any ideas?
Argh! When I moved the dma_configure call into iommu_init_device() for
v2 I moved the warning with it, but of course that needs to stay where
it was, *after* the point that ops->probe_device has had a chance to
filter out irrelevant devices. Does this make it behave?
Yes. It works on my end.
Thanks,
baolu
