From: Namhyung Kim <namhyung@kernel.org>
To: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
Aaron Tomlin <atomlin@atomlin.com>
Cc: mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@kernel.org, irogers@google.com, adrian.hunter@intel.com,
james.clark@linaro.org, howardchu95@gmail.com, neelx@suse.com,
chjohnst@mail.com, sean@ashe.io, steve@abita.co,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] perf trace: Correct cpumask formatting and add --bitmask-list
Date: Sat, 25 Jul 2026 22:23:56 -0700 [thread overview]
Message-ID: <178504343680.1075259.11521383454860356072.b4-ty@kernel.org> (raw)
In-Reply-To: <20260722155050.503516-1-atomlin@atomlin.com>
On Wed, 22 Jul 2026 11:50:47 -0400, Aaron Tomlin wrote:
> This series corrects cpumask formatting inside 'perf trace' and introduces
> a new command-line option to display these masks as human-readable CPU
> lists.
>
> Currently, when parsing tracepoints containing 'cpumask_t' fields (which
> are represented as dynamic non-array fields in libtraceevent), 'perf trace'
> incorrectly interprets and prints the raw length and offset descriptor as a
> decimal integer (i.e., "cpumask: 524320") rather than formatting the actual
> mask data.
>
> [...]
Applied to perf-tools-next, thanks!
Best regards,
Namhyung
prev parent reply other threads:[~2026-07-26 5:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 15:50 [PATCH v4 0/2] perf trace: Correct cpumask formatting and add --bitmask-list Aaron Tomlin
2026-07-22 15:50 ` [PATCH v4 1/2] perf trace: Correct default cpumask formatting to hexadecimal Aaron Tomlin
2026-07-22 15:50 ` [PATCH v4 2/2] perf trace: Add --bitmask-list command-line option Aaron Tomlin
2026-07-23 5:49 ` Namhyung Kim
2026-07-23 15:28 ` Aaron Tomlin
2026-07-24 5:54 ` Namhyung Kim
2026-07-24 14:25 ` Aaron Tomlin
2026-07-26 5:23 ` Namhyung Kim [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=178504343680.1075259.11521383454860356072.b4-ty@kernel.org \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=atomlin@atomlin.com \
--cc=chjohnst@mail.com \
--cc=howardchu95@gmail.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=neelx@suse.com \
--cc=peterz@infradead.org \
--cc=sean@ashe.io \
--cc=steve@abita.co \
/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