[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z-H87C_X63bH5QPw@google.com>
Date: Mon, 24 Mar 2025 17:46:36 -0700
From: Namhyung Kim <namhyung@...nel.org>
To: Ingo Molnar <mingo@...nel.org>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
Ian Rogers <irogers@...gle.com>,
Kan Liang <kan.liang@...ux.intel.com>, Jiri Olsa <jolsa@...nel.org>,
Adrian Hunter <adrian.hunter@...el.com>,
Peter Zijlstra <peterz@...radead.org>,
LKML <linux-kernel@...r.kernel.org>,
linux-perf-users@...r.kernel.org,
Dmitry Vyukov <dvyukov@...gle.com>
Subject: Re: [PATCH 1/3] perf sort: Keep output fields in the same level
On Thu, Mar 20, 2025 at 10:32:39AM +0100, Ingo Molnar wrote:
> 4)
>
> It would also be nice to have an export function to save current 'perf
> top' profiling data and have it available for 'perf report' et al
> analysis. Ie. frequently I just see an interesting snapshot and decide
> that it's good for further analysis, freeze the screen and are left
> with very few options to keep it for further look and reference.
I've thought about this but there are some limitations. Basically perf
top and perf report aggregates sammples into hist_entry's using the
given sort keys. That means other information in the samples are gone
already.
For perf top, it only has dso and symbol - plus number of samples and
the total periods. Other informations like CPU, PID and TIME are not
available so it cannot reconstruct samples precisely. So it's only
possible to use the same sort keys or a subset of them IMHO.
Do you think it'd be useful even with this?
Thanks,
Namhyung
Powered by blists - more mailing lists