projects / linux-2.6-block.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: ddf599c) | patch
io_uring: add opcode to issue trace event
authorJens Axboe <axboe@kernel.dk>
Thu, 9 Jan 2020 01:55:15 +0000 (18:55 -0700)
committerJens Axboe <axboe@kernel.dk>
Wed, 15 Jan 2020 22:05:04 +0000 (15:05 -0700)
commit3edcd3102675239ddc7b037af66be28f68d0656e
treeac2e08a74479a56dc29a136914bc3a627e9d9337tree
parentddf599cd7dc12197a1d7c3205b6231feb029bd13commit | diff
io_uring: add opcode to issue trace event

For some test apps at least, user_data is just zeroes. So it's not a
good way to tell what the command actually is. Add the opcode to the
issue trace point.

Signed-off-by: Jens Axboe <axboe@kernel.dk>
fs/io_uring.c diff | blob | blame | history
include/trace/events/io_uring.h diff | blob | blame | history
Linux 6.x block layer and io_uring tree(s)