From: Dylan Yudaken <[email protected]>
To: <[email protected]>
Cc: <[email protected]>, <[email protected]>, <[email protected]>,
Dylan Yudaken <[email protected]>
Subject: [PATCH 0/3] text representation of opcode in trace
Date: Mon, 25 Apr 2022 02:36:10 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
This series adds the text representation of opcodes into the trace. This
makes it much quicker to understand traces without having to translate
opcodes in your head.
Patch 1 is the translation function.
Patch 2 is a small cleanup
Patch 3 uses the translator in the trace logic
Dylan Yudaken (3):
io_uring: add io_uring_get_opcode
io_uring: rename op -> opcode
io_uring: use the text representation of ops in trace
fs/io_uring.c | 91 +++++++++++++++++++++++++++++++++
include/linux/io_uring.h | 5 ++
include/trace/events/io_uring.h | 42 +++++++++------
3 files changed, 121 insertions(+), 17 deletions(-)
base-commit: 155bc9505dbd6613585abbf0be6466f1c21536c4
--
2.30.2
next reply other threads:[~2022-04-25 9:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 9:36 Dylan Yudaken [this message]
2022-04-25 9:36 ` [PATCH 1/3] io_uring: add io_uring_get_opcode Dylan Yudaken
2022-04-25 12:38 ` Jens Axboe
2022-04-25 9:36 ` [PATCH 2/3] io_uring: rename op -> opcode Dylan Yudaken
2022-04-25 9:36 ` [PATCH 3/3] io_uring: use the text representation of ops in trace Dylan Yudaken
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox