Displaying 7 results from an estimated 7 matches for "function_graph".
2013 Aug 22
2
[PATCH] tracing/events: Add bounce tracing to swiotbl-xen
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-xen:bounced event, which also prints out the following
informations to help you find out why bouncing happened...
2013 Aug 22
2
[PATCH] tracing/events: Add bounce tracing to swiotbl-xen
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-xen:bounced event, which also prints out the following
informations to help you find out why bouncing happened...
2013 Aug 22
2
[PATCH] tracing/events: Add bounce tracing to swiotbl-xen
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-xen:bounced event, which also prints out the following
informations to help you find out why bouncing happened...
2013 Sep 04
1
[PATCHv2] 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 happ...
2013 Sep 04
1
[PATCHv2] 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 happ...
2013 Sep 04
1
[PATCHv2] 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 happ...
2009 Aug 03
1
Cannot boot Dom0: Thread overran stack, or stack corrupted
...] Testing tracer sched_switch: PASSED
[ 1.396782] Testing tracer sysprof: PASSED
[ 1.504844] Testing tracer function: PASSED
[ 1.617431] Testing tracer irqsoff: PASSED
[ 1.621818] Testing tracer wakeup: PASSED
[ 1.936759] Testing tracer wakeup_rt: PASSED
[ 2.248770] Testing tracer function_graph: <3>BUG: scheduling while atomic: swapper/1/0xdf803480
[ 2.253478] BUG: unable to handle kernel paging request at 3e87ab40
[ 2.253478] IP: [<c0107f29>] xen_iret+0x15/0x2b
[ 2.253478] *pdpt = 000000003c813001
[ 2.253478] Thread overran stack, or stack corrupted
[ 2.253478...