kernel.git/include/trace/events/btrfs.h, branch linux-3.18.y

Btrfs: fix wrong parse of extent map's tracepoint

2014-09-18T14:14:47Z

The tracepoint of extent map doesn't parse @flag correctly, we set @flag via set_bit(), so we need to parse it on a bit bias. Also add the missing flag, EXTENT_FLAG_FS_MAPPING. Signed-off-by: Liu Bo Signed-off-by: Chris Mason

Btrfs: show real function name in btrfs workqueue tracepoint

2014-09-17T20:38:18Z

Use %pf instead of %p, just same as kernel workqueue tracepoints. Signed-off-by: Liu Bo Reviewed-by: David Sterba Signed-off-by: Chris Mason

Btrfs: cleanup for btrfs workqueue tracepoints

2014-09-17T20:37:52Z

Tracepoint trace_btrfs_normal_work_done never has an user, just cleanup it. Signed-off-by: Liu Bo Signed-off-by: Chris Mason

Btrfs: add work_struct information for workqueue tracepoint

2014-09-17T20:37:51Z

Kernel workqueue's tracepoints print the address of work_struct, while btrfs workqueue's tracepoints print the address of btrfs_work. We need a connection between this two, for example when debuging, we usually grep an address in the trace output. So it'd be better to also print work_struct in btrfs workqueue's tracepoint. Please note that we can only add this into those tracepoints whose work is still available in memory because we need to reference the work. Signed-off-by: Liu Bo Signed-off-by: Chris Mason

btrfs: add trace for qgroup accounting

2014-09-17T20:37:50Z

We want this to debug qgroup changes on live systems. Signed-off-by: Mark Fasheh Reviewed-by: Josef Bacik Signed-off-by: Chris Mason

btrfs: Add trace for btrfs_workqueue alloc/destroy

2014-03-21T00:15:28Z

Since most of the btrfs_workqueue is printed as pointer address, for easier analysis, add trace for btrfs_workqueue alloc/destroy. So it is possible to determine the workqueue that a given work belongs to(by comparing the wq pointer address with alloc trace event). Signed-off-by: Qu Wenruo Signed-off-by: Chris Mason

btrfs: Add ftrace for btrfs_workqueue

2014-03-10T19:17:21Z

Add ftrace for btrfs_workqueue for further workqueue tunning. This patch needs to applied after the workqueue replace patchset. Signed-off-by: Qu Wenruo Signed-off-by: Josef Bacik

Btrfs/tracepoint: update new flags for ordered extent TP

2014-01-28T21:19:38Z

Flag BTRFS_ORDERED_TRUNCATED is a new one, update the tracepoint to support it. Signed-off-by: Liu Bo Signed-off-by: Josef Bacik Signed-off-by: Chris Mason

Btrfs/tracepoint: fix to report right flags for ordered extent

2014-01-28T21:19:38Z

We use set_bit() to assign ordered extent's flags, but in the related tracepoint we don't do the same thing, which makes the trace output not to parse flags correctly. Also, since the flags are bits stuff, we change to use __print_flags with a 'delim' instead of __print_symbolic. Signed-off-by: Liu Bo Signed-off-by: Josef Bacik Signed-off-by: Chris Mason

btrfs: Use trace condition for get_extent tracepoint

2013-11-21T01:44:47Z

Doing an if statement to test some condition to know if we should trigger a tracepoint is pointless when tracing is disabled. This just adds overhead and wastes a branch prediction. This is why the TRACE_EVENT_CONDITION() was created. It places the check inside the jump label so that the branch does not happen unless tracing is enabled. That is, instead of doing: if (em) trace_btrfs_get_extent(root, em); Which is basically this: if (em) if (static_key(trace_btrfs_get_extent)) { Using a TRACE_EVENT_CONDITION() we can just do: trace_btrfs_get_extent(root, em); And the condition trace event will do: if (static_key(trace_btrfs_get_extent)) { if (em) { ... The static key is a non conditional jump (or nop) that is faster than having to check if em is NULL or not. Signed-off-by: Steven Rostedt Signed-off-by: Josef Bacik Signed-off-by: Chris Mason