From: Jens Axboe <[email protected]>
To: [email protected], [email protected], [email protected]
Subject: Re: [PATCH 5.19] io_uring: move io_uring_get_opcode out of TP_printk
Date: Sat, 25 Jun 2022 06:48:52 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Thu, 23 Jun 2022 01:37:43 -0700, Dylan Yudaken wrote:
> The TP_printk macro's are not supposed to use custom code ([1]) or else
> tools such as perf cannot use these events.
>
> Convert the opcode string representation to use the __string wiring that
> the event framework provides ([2]).
>
> [1]: https://lwn.net/Articles/379903/
> [2]: https://lwn.net/Articles/381064/
>
> [...]
Applied, thanks!
[1/1] io_uring: move io_uring_get_opcode out of TP_printk
commit: e70b64a3f28b9f54602ae3e706b1dc1338de3df7
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-06-25 12:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 8:37 [PATCH 5.19] io_uring: move io_uring_get_opcode out of TP_printk Dylan Yudaken
2022-06-23 14:36 ` Jens Axboe
2022-06-23 14:59 ` Dylan Yudaken
2022-06-25 12:48 ` Jens Axboe [this message]
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 \
--in-reply-to=165616133228.53712.7999095570148197511.b4-ty@kernel.dk \
[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