[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z_rQMwKQDu6K66_r@gmail.com>
Date: Sat, 12 Apr 2025 22:42:27 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Ian Rogers <irogers@...gle.com>
Cc: Mark Barnett <mark.barnett@....com>, peterz@...radead.org,
mingo@...hat.com, acme@...nel.org, namhyung@...nel.org,
ben.gainey@....com, deepak.surti@....com, ak@...ux.intel.com,
will@...nel.org, james.clark@....com, mark.rutland@....com,
alexander.shishkin@...ux.intel.com, jolsa@...nel.org,
adrian.hunter@...el.com, linux-perf-users@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v4 0/5] A mechanism for efficient support for
per-function metrics
* Ian Rogers <irogers@...gle.com> wrote:
> I don't think work should be gated on cleaning up perf report, top,
> etc. which still needs clean up for things like hybrid events. As the
> histograms should use the sample's period then I believe things
> should just work in much the same way as leader sampling can work.
> It'd be worth checking.
Yeah, so I think burst-profiling is basically still a single-event
profiling mode - with a tooling-side filter that skips the long-periods
and includes the burst-periods, and transforms all the statistics and
counts to make sense in the usual perf context.
Ie. I don't think it should be overly intrusive, and it could be a nice
performance & profiling quality feature we'd consider using by default
eventually.
Thanks,
Ingo
Powered by blists - more mailing lists