For performance and debugging purposes, these trace events help
analyzing device faults and passdown invalidations that interact
with IOMMU subsystem.
E.g.
IOMMU:0000:00:0a.0 type=2 reason=0 addr=0x00000000007ff000 pasid=1
group=1 last=0 prot=1

Signed-off-by: Jacob Pan <jacob.jun....@linux.intel.com>
---
 drivers/iommu/iommu.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
index 1f2f49e..0108970 100644
--- a/drivers/iommu/iommu.c
+++ b/drivers/iommu/iommu.c
@@ -1006,6 +1006,7 @@ int iommu_report_device_fault(struct device *dev, struct 
iommu_fault_event *evt)
                mutex_unlock(&fparam->lock);
        }
        ret = fparam->handler(evt, fparam->data);
+       trace_dev_fault(dev, evt);
 done_unlock:
        mutex_unlock(&dev->iommu_param->lock);
        return ret;
@@ -1574,6 +1575,7 @@ int iommu_sva_invalidate(struct iommu_domain *domain,
                return -ENODEV;
 
        ret = domain->ops->sva_invalidate(domain, dev, inv_info);
+       trace_sva_invalidate(dev, inv_info);
 
        return ret;
 }
@@ -1611,6 +1613,7 @@ int iommu_page_response(struct device *dev,
                if (evt->pasid == msg->pasid &&
                    msg->page_req_group_id == evt->page_req_group_id) {
                        msg->private_data = evt->iommu_private;
+                       trace_dev_page_response(dev, msg);
                        ret = domain->ops->page_response(dev, msg);
                        list_del(&evt->list);
                        kfree(evt);
-- 
2.7.4

Reply via email to