Re: [PATCH] perf tests: Don't retest sections in "Object code reading"

From: Arnaldo Carvalho de Melo

Date: Mon Oct 06 2025 - 16:03:23 EST


On Mon, Oct 06, 2025 at 08:21:12AM -0700, Ian Rogers wrote:
> On Mon, Oct 6, 2025 at 6:11 AM James Clark <james.clark@xxxxxxxxxx> wrote:
> > We already only test each kcore map once, but on slow systems
> > (particularly with network filesystems) even the non-kcore maps are
> > slow. The test can test the same objump output over and over which only
> > wastes time. Generalize the skipping mechanism to track all DSOs and
> > addresses so that each section is only tested once.
> >
> > On a fully loaded Arm Juno (simulating a parallel Perf test run) with a
> > network filesystem, the original runtime is:
> >
> > real 1m51.126s
> > user 0m19.445s
> > sys 1m15.431s
> >
> > And the new runtime is:
> >
> > real 0m48.873s
> > user 0m8.031s
> > sys 0m32.353s
> >
> > Signed-off-by: James Clark <james.clark@xxxxxxxxxx>
>
> Reviewed-by: Ian Rogers <irogers@xxxxxxxxxx>

Thanks, applied to perf-tools-next,

- Arnaldo