On Thu, 15 Feb 2018 10:53:38 +0100 Joerg Roedel <j...@8bytes.org> wrote:
> On Tue, Feb 13, 2018 at 02:53:32PM -0800, Jacob Pan wrote: > > We did start out with /dev/mem but run into CONFIG_STRICT_DEVMEM > > requirement which is turned on by default. > > libpci is only limited to PCI config space access, right? > > Even if /dev/mem is not an option, I am still not convinced that this > is a good idea. How should this be used? Will you just use it to debug > Intel IOMMUs when you guys work on the driver or should users report > the data back when they hit problems? > It is for both but mainly the latter. when we have customers/users reporting Intel IOMMU issues, it would be extremely helpful if we can ask them to turn debugfs on and report the state. As we move to SVA, we may also include io page table similar to /sys/kernel/debug/page_table for PASID etc. Just wondering if your concern is on the implementation or the debugfs idea in general. Perhaps have some common IOMMU debugfs? _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu
