[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAM9d7cgE6vcB0Pi+585JKaddiRGOFkFFEiDP_FS-x6-2itVtfA@mail.gmail.com>
Date: Thu, 12 Oct 2023 10:24:21 -0700
From: Namhyung Kim <namhyung@...il.com>
To: Besar Wicaksono <bwicaksono@...dia.com>
Cc: james.clark@....com, mike.leach@...aro.org, suzuki.poulose@....com,
acme@...nel.org, linux-perf-users@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
coresight@...ts.linaro.org, linux-tegra@...r.kernel.org,
treding@...dia.com, jonathanh@...dia.com, vsethi@...dia.com,
rwiley@...dia.com, ywan@...dia.com
Subject: Re: [PATCH v3] perf cs-etm: Fix incorrect or missing decoder for raw trace
On Tue, Oct 10, 2023 at 4:49 PM Besar Wicaksono <bwicaksono@...dia.com> wrote:
>
> The decoder creation for raw trace uses metadata from the first CPU.
> On per-cpu mode, this metadata is incorrectly used for every decoder.
> On per-process/per-thread traces, the first CPU is CPU0. If CPU0 trace
> is not enabled, its metadata will be marked unused and the decoder is
> not created. Perf report dump skips the decoding part because the
> decoder is missing.
>
> To fix this, use metadata of the CPU associated with sample object.
>
> Signed-off-by: Besar Wicaksono <bwicaksono@...dia.com>
> Reviewed-by: James Clark <james.clark@....com>
Applied to perf-tools-next, thanks!
Powered by blists - more mailing lists