All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Aaron Tomlin" <atomlin@atomlin.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v2] perf trace: Support --bitmask-list with --libtraceevent
Date: Sun, 04 Oct 2026 12:27:39 +0000	[thread overview]
Message-ID: <20261004122739.EED361F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20261004121531.380660-1-atomlin@atomlin.com>

> Commit ab74d1fbe061 ("perf trace: Add --bitmask-list command-line option")
> introduced the --bitmask-list option to display cpumasks and bitmasks as
> condensed, human-readable range lists (e.g. "0,2-5,7") instead of the
> default hexadecimal format.
> 
> However, that implementation only augmented trace__fprintf_tp_fields().
> When --libtraceevent is specified, event formatting is delegated to
> event_format__fprintf(), which bypasses trace__fprintf_tp_fields() and
> relies directly on libtraceevent.
> 
> In libtraceevent, tracepoint bitmask fields defined using __get_bitmask()
> are parsed into TEP_PRINT_BITMASK AST nodes and unconditionally formatted
> as raw 32-bit hex chunks (e.g. "00000000,00000005"), ignoring the
> --bitmask-list command-line option.
> 
> [ ... ]
> recording replay (trace__replay()), leaving trace__event_handler()
> untouched. As with existing tracepoint replay in perf trace, this expects
> the evlist to be populated from the session header.
> 
> Signed-off-by: Aaron Tomlin <atomlin@atomlin.com>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261004121531.380660-1-atomlin@atomlin.com?part=1


      reply	other threads:[~2026-10-04 12:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-04 12:15 [PATCH v2] perf trace: Support --bitmask-list with --libtraceevent Aaron Tomlin
2026-10-04 12:27 ` sashiko-bot [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=20261004122739.EED361F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=atomlin@atomlin.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.