linux-toradex.git/include/linux/blktrace_api.h, branch v4.14-rc7

block: use standard blktrace API to output cgroup info for debug notes

2017-07-29T15:00:03+00:00

Currently cfq/bfq/blk-throttle output cgroup info in trace in their own
way. Now we have standard blktrace API for this, so convert them to use
it.

Note, this changes the behavior a little bit. cgroup info isn't output
by default, we only do this with 'blk_cgroup' option enabled. cgroup
info isn't output as a string by default too, we only do this with
'blk_cgname' option enabled. Also cgroup info is output in different
position of the note string. I think these behavior changes aren't a big
issue (actually we make trace data shorter which is good), since the
blktrace note is solely for debugging.

Signed-off-by: Shaohua Li 
Signed-off-by: Jens Axboe

blktrace: make do_blk_trace_setup() static

2017-02-02T17:20:16+00:00

This isn't used outside of blktrace.c anymore.

Fixes: 62c2a7d969f3 ("block: push BKL into blktrace ioctls")
Signed-off-by: Omar Sandoval 
Signed-off-by: Jens Axboe

block: introduce blk_rq_is_passthrough

2017-01-31T21:00:34+00:00

This can be used to check for fs vs non-fs requests and basically
removes all knowledge of BLOCK_PC specific from the block layer,
as well as preparing for removing the cmd_type field in struct request.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Jens Axboe

block: cleanup tracing

2017-01-27T22:08:35+00:00

A couple tweaks to the tracing code:

 - trace the request size for all requests
 - trace request sector and nr_sectors only for fs requests, enforced by
   helpers
 - drop SCSI CDB tracing - we have SCSI tracing for this and are going
   to me the CDB out of the generic struct request soon.

With this the tracing code stops to know about BLOCK_PC requests entirely,
it's just FS vs passthrough requests now, where the latter includes any
driver-private requests.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Jens Axboe

block: better op and flags encoding

2016-10-28T14:48:16+00:00

Now that we don't need the common flags to overflow outside the range
of a 32-bit type we can encode them the same way for both the bio and
request fields.  This in addition allows us to place the operation
first (and make some room for more ops while we're at it) and to
stop having to shift around the operation values.

In addition this allows passing around only one value in the block layer
instead of two (and eventuall also in the file systems, but we can do
that later) and thus clean up a lot of code.

Last but not least this allows decreasing the size of the cmd_flags
field in struct request to 32-bits.  Various functions passing this
value could also be updated, but I'd like to avoid the churn for now.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Jens Axboe

blktrace: use op accessors

2016-06-07T19:41:38+00:00

Have blktrace use the req/bio op accessor to get the REQ_OP.

Signed-off-by: Mike Christie 
Reviewed-by: Christoph Hellwig 
Reviewed-by: Hannes Reinecke 
Signed-off-by: Jens Axboe

blk-throttle: don't parse cgroup path if trace isn't enabled

2016-05-10T14:41:37+00:00

if trace isn't enabled, parsing cgroup path just wastes cpu

Signed-off-by: Shaohua Li 
Signed-off-by: Jens Axboe

kernel: trace: blktrace: remove redundent memcpy() in compat_blk_trace_setup()

2013-11-08T16:04:30+00:00

do_blk_trace_setup() will fully initialize 'buts.name', so can remove
the related memcpy(). And also use BLKTRACE_BDEV_SIZE and ARRAY_SIZE
instead of hard code number '32'.

Signed-off-by: Chen Gang 
Signed-off-by: Jens Axboe

blktrace: Send BLK_TN_PROCESS events to all running traces

2013-11-08T15:59:00+00:00

Currently each task sends BLK_TN_PROCESS event to the first traced
device it interacts with after a new trace is started. When there are
several traced devices and the task accesses more devices, this logic
can result in BLK_TN_PROCESS being sent several times to some devices
while it is never sent to other devices. Thus blkparse doesn't display
command name when parsing some blktrace files.

Fix the problem by sending BLK_TN_PROCESS event to all traced devices
when a task interacts with any of them.

Signed-off-by: Jan Kara 
Review-by: Jeff Moyer 
Signed-off-by: Jens Axboe

Revert "block: add missing block_bio_complete() tracepoint"

2013-04-18T16:00:26+00:00

This reverts commit 3a366e614d0837d9fc23f78cdb1a1186ebc3387f.

Wanlong Gao reports that it causes a kernel panic on his machine several
minutes after boot. Reverting it removes the panic.

Jens says:
 "It's not quite clear why that is yet, so I think we should just revert
  the commit for 3.9 final (which I'm assuming is pretty close).

  The wifi is crap at the LSF hotel, so sending this email instead of
  queueing up a revert and pull request."

Reported-by: Wanlong Gao 
Requested-by: Jens Axboe 
Cc: Tejun Heo 
Cc: Steven Rostedt 
Signed-off-by: Linus Torvalds