diff options
| author | David Woodhouse <dwmw2@infradead.org> | 2009-02-12 16:19:13 +0100 |
|---|---|---|
| committer | Joerg Roedel <joerg.roedel@amd.com> | 2009-03-17 12:56:39 +0100 |
| commit | ac26c18bd35d982d1ba06020a992b1085fefc3e2 (patch) | |
| tree | 33f7fe1a22848c7dfdd002298f27efff103480a4 /lib/dma-debug.c | |
| parent | a31fba5d68cebf8f5fefd03e079dab94875e25f5 (diff) | |
dma-debug: add function to dump dma mappings
This adds a function to dump the DMA mappings that the debugging code is
aware of -- either for a single device, or for _all_ devices.
This can be useful for debugging -- sticking a call to it in the DMA
page fault handler, for example, to see if the faulting address _should_
be mapped or not, and hence work out whether it's IOMMU bugs we're
seeing, or driver bugs.
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
Diffstat (limited to 'lib/dma-debug.c')
| -rw-r--r-- | lib/dma-debug.c | 30 |
1 files changed, 30 insertions, 0 deletions
diff --git a/lib/dma-debug.c b/lib/dma-debug.c index 9d11e89c2ee..91ed1dfdbaa 100644 --- a/lib/dma-debug.c +++ b/lib/dma-debug.c @@ -194,6 +194,36 @@ static void hash_bucket_del(struct dma_debug_entry *entry) } /* + * Dump mapping entries for debugging purposes + */ +void debug_dma_dump_mappings(struct device *dev) +{ + int idx; + + for (idx = 0; idx < HASH_SIZE; idx++) { + struct hash_bucket *bucket = &dma_entry_hash[idx]; + struct dma_debug_entry *entry; + unsigned long flags; + + spin_lock_irqsave(&bucket->lock, flags); + + list_for_each_entry(entry, &bucket->list, list) { + if (!dev || dev == entry->dev) { + dev_info(entry->dev, + "%s idx %d P=%Lx D=%Lx L=%Lx %s\n", + type2name[entry->type], idx, + (unsigned long long)entry->paddr, + entry->dev_addr, entry->size, + dir2name[entry->direction]); + } + } + + spin_unlock_irqrestore(&bucket->lock, flags); + } +} +EXPORT_SYMBOL(debug_dma_dump_mappings); + +/* * Wrapper function for adding an entry to the hash. * This function takes care of locking itself. */ |