From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joerg Roedel Subject: Re: [PATCH 0/16] DMA-API debugging facility v2 Date: Thu, 12 Feb 2009 16:20:27 +0100 Message-ID: <20090212152027.GE2125@8bytes.org> References: <1231517970-20288-1-git-send-email-joerg.roedel@amd.com> <1233874352.8135.12.camel@macbook.infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Joerg Roedel , fujita.tomonori@lab.ntt.co.jp, netdev@vger.kernel.org, iommu@lists.linux-foundation.org, mingo@redhat.com, linux-kernel@vger.kernel.org To: David Woodhouse Return-path: Received: from 8bytes.org ([88.198.83.132]:59700 "EHLO 8bytes.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750742AbZBLPU2 (ORCPT ); Thu, 12 Feb 2009 10:20:28 -0500 Content-Disposition: inline In-Reply-To: <1233874352.8135.12.camel@macbook.infradead.org> Sender: netdev-owner@vger.kernel.org List-ID: On Thu, Feb 05, 2009 at 10:52:32PM +0000, David Woodhouse wrote: > 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 > Great. Thanks. Applied to my dma-api/debug branch. Joerg