From: James Clark <james.clark@linaro.org>
To: Leo Yan <leo.yan@arm.com>
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Tamas Petz <tamas.petz@arm.com>,
Tamas Zsoldos <tamas.zsoldos@arm.com>
Subject: Re: [PATCH] perf/core: Skip empty AUX records with only format flags
Date: Wed, 26 Aug 2026 09:52:51 +0100 [thread overview]
Message-ID: <d99b2248-14b6-4e79-b691-efba443a17ed@linaro.org> (raw)
In-Reply-To: <20260825-perf_core_fix_zero_aux_records-v1-1-23b95e8d5df3@arm.com>
On 25/08/2026 11:37, Leo Yan wrote:
> perf_aux_output_end() emits a PERF_RECORD_AUX when the recorded size is
> nonzero or when any flag other than PERF_AUX_FLAG_OVERWRITE is set.
>
> PMU format flags describe how an AUX payload is encoded. TRBE driver
> sets PERF_AUX_FLAG_CORESIGHT_FORMAT_RAW for raw trace buffers, causing
> an AUX record to be emitted even when no trace data.
>
> This is noticeable when tracing a task with strace. Ptrace stops
> repeatedly end empty AUX transactions, producing many zero-sized
> PERF_RECORD_AUX records. For example:
>
> perf record -e cs_etm//u -m,128M -- strace ls
>
> perf script -D 2>&1 |
> awk '/PERF_RECORD_AUX offset/ {
> for (i = 1; i <= NF; i++)
> if ($i == "size:" && $(i + 1) == "0")
> count++
> }
> END { print count }'
> 165
>
> This recording contains 165 zero-sized AUX records which provide no
> useful information to userspace.
>
> Ignore PERF_AUX_FLAG_PMU_FORMAT_TYPE_MASK, together with
> PERF_AUX_FLAG_OVERWRITE, when deciding whether an empty AUX record is
> useful. Zero-sized records carrying TRUNCATED, PARTIAL or COLLISION
> are still emitted.
>
> Fixes: 547b60988e63 ("perf: aux: Add flags for the buffer format")
> Reported-by: Tamas Petz <tamas.petz@arm.com>
> Signed-off-by: Leo Yan <leo.yan@arm.com>
> ---
> kernel/events/ring_buffer.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/events/ring_buffer.c b/kernel/events/ring_buffer.c
> index 9fe92161715e0987520cddb873dd162fd2a77d5c..1b1ffe0533e58a9d976d0eb0fc23e09d5936da2b 100644
> --- a/kernel/events/ring_buffer.c
> +++ b/kernel/events/ring_buffer.c
> @@ -509,7 +509,10 @@ void perf_aux_output_end(struct perf_output_handle *handle, unsigned long size)
> /*
> * Only send RECORD_AUX if we have something useful to communicate
> *
> - * Note: the OVERWRITE records by themselves are not considered
> + * PMU_FORMAT bits identify the PMU type rather than an AUX event
> + * has occurred, so ignore them for zero-sized records.
> + *
> + * The OVERWRITE records by themselves are not considered
> * useful, as they don't communicate any *new* information,
> * aside from the short-lived offset, that becomes history at
> * the next event sched-in and therefore isn't useful.
> @@ -518,7 +521,9 @@ void perf_aux_output_end(struct perf_output_handle *handle, unsigned long size)
> * offset. So, from now on we don't output AUX records that
> * have *only* OVERWRITE flag set.
> */
> - if (size || (handle->aux_flags & ~(u64)PERF_AUX_FLAG_OVERWRITE))
> + if (size ||
> + (handle->aux_flags & ~(u64)(PERF_AUX_FLAG_PMU_FORMAT_TYPE_MASK |
> + PERF_AUX_FLAG_OVERWRITE)))
Almost seems like it would be better to define the union of what's
considered useful where they are defined in perf_event.h. Or invert it
here and do (TRUNCATED | PARTIAL etc). Otherwise the same thing will
happen when the next thing is added.
Other than that:
Reviewed-by: James Clark <james.clark@linaro.org>
> perf_event_aux_event(handle->event, aux_head, size,
> handle->aux_flags);
>
>
> ---
> base-commit: 66498c75b4f8017f62d720d9b59675bdf3abce91
> change-id: 20260825-perf_core_fix_zero_aux_records-8873172d2596
>
> Best regards,
prev parent reply other threads:[~2026-08-26 8:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 10:37 [PATCH] perf/core: Skip empty AUX records with only format flags Leo Yan
2026-08-25 10:44 ` sashiko-bot
2026-08-26 8:52 ` James Clark [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=d99b2248-14b6-4e79-b691-efba443a17ed@linaro.org \
--to=james.clark@linaro.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=leo.yan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=suzuki.poulose@arm.com \
--cc=tamas.petz@arm.com \
--cc=tamas.zsoldos@arm.com \
/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