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,
rishil1999@outlook.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] perf trace: Format fields with hex specifiers in print_fmt as hexadecimal
Date: Wed, 05 Aug 2026 11:28:16 -0700 [thread overview]
Message-ID: <178595449650.914389.87119431734742911.b4-ty@kernel.org> (raw)
In-Reply-To: <20260803124845.213165-1-atomlin@atomlin.com>
On Mon, 03 Aug 2026 08:48:45 -0400, Aaron Tomlin wrote:
> Currently, when a probe event is added using perf probe --add with a
> hexadecimal type cast (e.g., var:x64 and var:x32), the kernel traceprobe
> subsystem sets the field type to "u64" in the event's format file, yet
> generates a print format specifier of "var=0x%Lx" or "0x%x".
>
> By default, perf trace uses its internal beautifiers which only inspect
> field->type and field->flags. Because traceprobe events declare
> primitive integer field types ("u64") without a C pointer asterisk
> (i.e., "*"), perf trace defaults to printing the field's value as a
> decimal unsigned long ("%ld"), ignoring the hexadecimal intent.
>
> [...]
Applied to perf-tools-next, thanks!
Best regards,
Namhyung
next prev parent reply other threads:[~2026-08-05 18:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 12:48 Aaron Tomlin
2026-08-05 18:28 ` Namhyung Kim [this message]
2026-08-05 18:53 ` Aaron Tomlin
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=178595449650.914389.87119431734742911.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=rishil1999@outlook.com \
--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
all inboxes | Powered by JetHome®