Zoltan Kiss 2b2b614dd2 tracing/events: Add bounce tracing to swiotbl
Ftrace is currently not able to detect when SWIOTLB has to do double buffering.
Under Xen you can only see it indirectly in function_graph, when
xen_swiotlb_map_page() doesn't stop after range_straddles_page_boundary(), but
calls spinlock functions, memcpy() and xen_phys_to_bus() as well. This patch
introduces the swiotlb:swiotlb_bounced event, which also prints out the
following informations to help you find out why bouncing happened:

dev_name: 0000:08:00.0 dma_mask=ffffffffffffffff dev_addr=9149f000 size=32768
swiotlb_force=0

If you use Xen, and (dev_addr + size + 1) > dma_mask, the buffer is out of the
device's DMA range. If swiotlb_force == 1, you should really change the kernel
parameters. Otherwise, the buffer is not contiguous in mfn space.

Signed-off-by: Zoltan Kiss <zoltan.kiss@citrix.com>
[v1: Don't print 'swiotlb_force=X', just print swiotlb_force if it is enabled]
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
2013-10-02 12:53:26 -04:00
..
2013-07-19 13:54:23 -07:00
2013-09-10 13:03:41 -07:00
2013-03-13 15:21:48 -07:00
2011-03-11 14:25:50 +00:00
2008-06-06 11:29:10 -07:00
2013-07-09 10:33:30 -07:00
2011-10-29 21:20:22 +02:00
2011-03-31 11:26:23 -03:00
2013-02-27 19:10:09 -08:00
2012-10-06 03:04:57 +09:00
2013-01-17 12:19:09 -08:00
2012-10-09 16:22:40 +09:00
2013-06-18 13:48:45 +02:00
2012-12-17 17:15:22 -08:00
2012-07-30 17:25:16 -07:00
2012-01-31 23:19:47 +02:00
2013-09-09 14:29:15 -07:00
2011-12-08 19:52:43 -05:00
2013-04-29 18:28:42 -07:00