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>
This commit is contained in:
@@ -4810,7 +4810,8 @@ static int io_submit_sqes(struct io_ring_ctx *ctx, unsigned int nr,
|
||||
req->has_user = *mm != NULL;
|
||||
req->in_async = async;
|
||||
req->needs_fixed_file = async;
|
||||
trace_io_uring_submit_sqe(ctx, req->user_data, true, async);
|
||||
trace_io_uring_submit_sqe(ctx, req->opcode, req->user_data,
|
||||
true, async);
|
||||
if (!io_submit_sqe(req, sqe, statep, &link))
|
||||
break;
|
||||
}
|
||||
|
Reference in New Issue
Block a user