From: David Woodhouse <dwmw2@infradead.org>
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com,
fujita.tomonori@lab.ntt.co.jp, netdev@vger.kernel.org,
iommu@lists.linux-foundation.org
Subject: Re: [PATCH 0/16] DMA-API debugging facility v2
Date: Thu, 05 Feb 2009 22:52:32 +0000 [thread overview]
Message-ID: <1233874352.8135.12.camel@macbook.infradead.org> (raw)
In-Reply-To: <1231517970-20288-1-git-send-email-joerg.roedel@amd.com>
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.
I'd also like to make it answer the question 'should address X be mapped
for device Y', but I'll get to that next.
Do we have a %pX format for printing dma_addr_t yet?
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
diff --git a/include/linux/dma-debug.h b/include/linux/dma-debug.h
index 8a8aae4..5f4fc9f 100644
--- a/include/linux/dma-debug.h
+++ b/include/linux/dma-debug.h
@@ -75,6 +75,8 @@ extern void debug_dma_sync_sg_for_device(struct device *dev,
struct scatterlist *sg,
int nelems, int direction);
+extern void debug_dma_dump_mappings(struct device *dev);
+
#else /* CONFIG_DMA_API_DEBUG */
static inline void dma_debug_init(u32 num_entries)
@@ -155,6 +157,10 @@ static inline void debug_dma_sync_sg_for_device(struct device *dev,
{
}
+static inline void debug_dma_dump_mappings(struct device *dev)
+{
+}
+
#endif /* CONFIG_DMA_API_DEBUG */
#endif /* __DMA_DEBUG_H */
diff --git a/lib/dma-debug.c b/lib/dma-debug.c
index 469e5b9..127d108 100644
--- a/lib/dma-debug.c
+++ b/lib/dma-debug.c
@@ -191,6 +191,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.
*/
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next prev parent reply other threads:[~2009-02-05 22:52 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 16:19 [PATCH 0/16] DMA-API debugging facility v2 Joerg Roedel
2009-01-09 16:19 ` [PATCH 01/16] dma-debug: add Kconfig entry Joerg Roedel
2009-01-09 20:12 ` Randy Dunlap
2009-01-09 16:19 ` [PATCH 02/16] dma-debug: add header file and core data structures Joerg Roedel
2009-01-11 6:25 ` FUJITA Tomonori
2009-01-09 16:19 ` [PATCH 03/16] dma-debug: add hash functions for dma_debug_entries Joerg Roedel
2009-01-09 17:55 ` Evgeniy Polyakov
2009-01-09 18:14 ` Joerg Roedel
2009-01-09 18:23 ` Evgeniy Polyakov
2009-01-09 18:40 ` Joerg Roedel
2009-01-13 8:51 ` Andrew Morton
2009-01-13 8:59 ` David Woodhouse
2009-01-14 11:43 ` Ingo Molnar
2009-01-14 17:39 ` Andrew Morton
2009-01-14 17:43 ` Ingo Molnar
2009-01-14 17:48 ` Ingo Molnar
2009-01-15 3:44 ` FUJITA Tomonori
2009-01-14 17:48 ` David Woodhouse
2009-01-14 17:51 ` Joerg Roedel
2009-01-09 16:19 ` [PATCH 04/16] dma-debug: add allocator code Joerg Roedel
2009-01-10 23:43 ` Ingo Molnar
2009-01-09 16:19 ` [PATCH 05/16] dma-debug: add initialization code Joerg Roedel
2009-01-09 17:58 ` Evgeniy Polyakov
2009-01-09 18:17 ` Joerg Roedel
2009-01-09 16:19 ` [PATCH 06/16] dma-debug: add kernel command line parameters Joerg Roedel
2009-01-09 16:19 ` [PATCH 07/16] dma-debug: add debugfs interface Joerg Roedel
2009-01-10 23:08 ` Ingo Molnar
2009-01-11 7:52 ` Joerg Roedel
2009-01-14 15:22 ` Joerg Roedel
2009-01-10 23:15 ` Ingo Molnar
2009-01-09 16:19 ` [PATCH 08/16] dma-debug: add core checking functions Joerg Roedel
2009-01-10 23:11 ` Ingo Molnar
2009-01-11 7:57 ` Joerg Roedel
2009-01-11 8:34 ` Joerg Roedel
2009-01-14 11:44 ` Joerg Roedel
2009-01-14 11:48 ` Ingo Molnar
2009-01-10 23:12 ` Ingo Molnar
2009-01-11 7:54 ` Joerg Roedel
2009-01-10 23:13 ` Ingo Molnar
2009-01-09 16:19 ` [PATCH 09/16] dma-debug: add checking for map/unmap_single Joerg Roedel
2009-01-09 16:19 ` [PATCH 10/16] dma-debug: add add checking for map/unmap_sg Joerg Roedel
2009-01-09 18:08 ` Evgeniy Polyakov
2009-01-09 18:11 ` Joerg Roedel
2009-01-09 16:19 ` [PATCH 11/16] dma-debug: add checking for [alloc|free]_coherent Joerg Roedel
2009-01-11 6:25 ` FUJITA Tomonori
2009-01-11 6:30 ` FUJITA Tomonori
2009-01-11 7:59 ` Joerg Roedel
2009-01-09 16:19 ` [PATCH 12/16] dma-debug: add checks for sync_single_* Joerg Roedel
2009-01-09 16:19 ` [PATCH 13/16] dma-debug: add checks for sync_single_range_* Joerg Roedel
2009-01-09 16:19 ` [PATCH 14/16] dma-debug: add checks for sync_single_sg_* Joerg Roedel
2009-01-10 23:46 ` Ingo Molnar
2009-01-11 8:00 ` Joerg Roedel
2009-01-09 16:19 ` [PATCH 15/16] dma-debug: x86 architecture bindings Joerg Roedel
2009-01-10 23:04 ` Ingo Molnar
2009-01-10 23:48 ` Ingo Molnar
2009-01-11 6:25 ` FUJITA Tomonori
2009-01-11 8:08 ` Joerg Roedel
2009-01-09 16:19 ` [PATCH 16/16] dma-debug: Documentation update Joerg Roedel
2009-01-09 21:24 ` [PATCH 0/16] DMA-API debugging facility v2 Michael Chan
2009-01-09 22:33 ` Joerg Roedel
2009-01-09 22:37 ` Joerg Roedel
2009-01-11 6:25 ` FUJITA Tomonori
2009-01-10 23:54 ` Ingo Molnar
2009-01-11 8:11 ` Joerg Roedel
2009-02-05 22:52 ` David Woodhouse [this message]
2009-02-06 2:05 ` Chris Wright
2009-02-06 7:56 ` David Woodhouse
2009-02-06 16:08 ` Chris Wright
2009-02-06 18:20 ` Chris Wright
2009-02-12 14:48 ` Joerg Roedel
2009-02-06 2:27 ` Chris Wright
2009-02-12 15:20 ` Joerg Roedel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1233874352.8135.12.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=iommu@lists.linux-foundation.org \
--cc=joerg.roedel@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).