public inbox for [email protected]
 help / color / mirror / Atom feed
From: Dylan Yudaken <[email protected]>
To: <[email protected]>
Cc: <[email protected]>, <[email protected]>, <[email protected]>,
	Dylan Yudaken <[email protected]>
Subject: [PATCH v3 0/4] io_uring: text representation of opcode in trace
Date: Tue, 26 Apr 2022 01:29:03 -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 adds a type to io_uring opcodes
Patch 2 is the translation function.
Patch 3 is a small cleanup
Patch 4 uses the translator in the trace logic

v2:
 - return "INVALID" rather than UNKNOWN/LAST
 - add a type to io_uring opcdodes to get the compiler to complain if any are
   missing

v3:
  - rebase onto for-5.19/io_uring-socket

Dylan Yudaken (4):
  io_uring: add type to op enum
  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                   | 101 ++++++++++++++++++++++++++++++++
 include/linux/io_uring.h        |   5 ++
 include/trace/events/io_uring.h |  42 +++++++------
 include/uapi/linux/io_uring.h   |   2 +-
 4 files changed, 132 insertions(+), 18 deletions(-)


base-commit: 1374e08e2d44863c931910797852589803997668
-- 
2.30.2


             reply	other threads:[~2022-04-26  8:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26  8:29 Dylan Yudaken [this message]
2022-04-26  8:29 ` [PATCH v3 1/4] io_uring: add type to op enum Dylan Yudaken
2022-04-26  8:29 ` [PATCH v3 2/4] io_uring: add io_uring_get_opcode Dylan Yudaken
2022-04-26  8:29 ` [PATCH v3 3/4] io_uring: rename op -> opcode Dylan Yudaken
2022-04-26  8:29 ` [PATCH v3 4/4] io_uring: use the text representation of ops in trace Dylan Yudaken
2022-04-26 12:51 ` [PATCH v3 0/4] io_uring: text representation of opcode " Jens Axboe

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