android_kernel_xiaomi_sm8350/include/trace
Jens Axboe 49cac01e1f block: make unplug timer trace event correspond to the schedule() unplug
It's a pretty close match to what we had before - the timer triggering
would mean that nobody unplugged the plug in due time, in the new
scheme this matches very closely what the schedule() unplug now is.
It's essentially the difference between an explicit unplug (IO unplug)
or an implicit unplug (timer unplug, we scheduled with pending IO
queued).

Signed-off-by: Jens Axboe <jaxboe@fusionio.com>
2011-04-16 13:51:05 +02:00
..
events block: make unplug timer trace event correspond to the schedule() unplug 2011-04-16 13:51:05 +02:00
define_trace.h tracing: Include module.h in define_trace.h 2011-01-07 15:44:56 -05:00
ftrace.h tracing: Replace trace_event struct array with pointer array 2011-02-02 21:37:13 -05:00
syscall.h