iommu: Log iova range in map/unmap trace events

In case of an iommu page fault, the faulting iova is logged
in trace_io_page_fault. It is therefore convenient to log
the iova range in mapping/unmapping trace events so that it
is easier to see if the faulting iova was recently in any of
those ranges.

Signed-off-by: Dafna Hirschfeld <dafna.hirschfeld@collabora.com>
Link: https://lore.kernel.org/r/20211104071620.27290-1-dafna.hirschfeld@collabora.com
Signed-off-by: Joerg Roedel <jroedel@suse.de>
This commit is contained in:
Dafna Hirschfeld 2021-11-04 09:16:20 +02:00 committed by Joerg Roedel
parent 0fcfb00b28
commit 94aedac49d
1 changed files with 6 additions and 4 deletions

View File

@ -101,8 +101,9 @@ TRACE_EVENT(map,
__entry->size = size;
),
TP_printk("IOMMU: iova=0x%016llx paddr=0x%016llx size=%zu",
__entry->iova, __entry->paddr, __entry->size
TP_printk("IOMMU: iova=0x%016llx - 0x%016llx paddr=0x%016llx size=%zu",
__entry->iova, __entry->iova + __entry->size, __entry->paddr,
__entry->size
)
);
@ -124,8 +125,9 @@ TRACE_EVENT(unmap,
__entry->unmapped_size = unmapped_size;
),
TP_printk("IOMMU: iova=0x%016llx size=%zu unmapped_size=%zu",
__entry->iova, __entry->size, __entry->unmapped_size
TP_printk("IOMMU: iova=0x%016llx - 0x%016llx size=%zu unmapped_size=%zu",
__entry->iova, __entry->iova + __entry->size,
__entry->size, __entry->unmapped_size
)
);