From: Aaron Tomlin <atomlin@atomlin.com>
To: rostedt@goodmis.org, mhiramat@kernel.org, mark.rutland@arm.com,
mathieu.desnoyers@efficios.com, corbet@lwn.net
Cc: sean@ashe.io, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: [v2 PATCH 0/1] tracing: Add bitmask-list option for human-readable bitmask display
Date: Thu, 25 Dec 2025 03:02:15 -0500 [thread overview]
Message-ID: <20251225080216.2196411-1-atomlin@atomlin.com> (raw)
Hi Steve,
Add support for displaying bitmasks in human-readable list format (e.g.,
0,2-5,7) in addition to the default hexadecimal bitmap representation.
This is particularly useful when tracing CPU masks and other large
bitmasks where individual bit positions are more meaningful than their
hexadecimal encoding.
When the "bitmask-list" option is enabled, the printk "%*pbl" format
specifier is used to render bitmasks as comma-separated ranges, making
trace output easier to interpret for complex CPU configurations and
large bitmask values.
This iteration incorporates the use of iter->tmp_seq to ensure the
implementation is robust, instance-aware, and free from buffer contention
or duplication issues.
Please let me know your thoughts.
Changes since v1 [1]:
- Introduce new helper trace_seq_bitmask_list() (Steven Rostedt)
- Use iter->tmp_seq as a scratchpad to prevent buffer collisions and
duplication
- Update trace_print_bitmask_seq() signature to accept trace_iterator
instead of trace_seq
- Add declaration for trace_seq_bitmask_list() and provide necessary stub
definitions
- Update __get_bitmask and __get_rel_bitmask macros to pass iter to the
bitmask helper
- Implement instance-aware bitmask formatting using iter->tmp_seq as a
scratchpad to prevent buffer collisions and duplication
[1]: https://lore.kernel.org/lkml/20251223035622.2084081-1-atomlin@atomlin.com/
Aaron Tomlin (1):
tracing: Add bitmask-list option for human-readable bitmask display
Documentation/trace/ftrace.rst | 9 +++++++
include/linux/trace_events.h | 8 +++---
include/linux/trace_seq.h | 12 ++++++++-
include/trace/stages/stage3_trace_output.h | 4 +--
kernel/trace/trace.h | 1 +
kernel/trace/trace_output.c | 30 +++++++++++++++++++---
kernel/trace/trace_seq.c | 29 ++++++++++++++++++++-
7 files changed, 82 insertions(+), 11 deletions(-)
--
2.51.0
next reply other threads:[~2025-12-25 8:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-25 8:02 Aaron Tomlin [this message]
2025-12-25 8:02 ` [v2 PATCH 1/1] tracing: Add bitmask-list option for human-readable bitmask display Aaron Tomlin
2025-12-26 2:53 ` kernel test robot
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=20251225080216.2196411-1-atomlin@atomlin.com \
--to=atomlin@atomlin.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sean@ashe.io \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).