[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAP-5=fUxY1KYXN-HcJPd2D66j5cC6DFTGPzYFVvJKvBLqyz6-Q@mail.gmail.com>
Date: Thu, 6 Feb 2025 10:51:16 -0800
From: Ian Rogers <irogers@...gle.com>
To: Dmitry Vyukov <dvyukov@...gle.com>
Cc: Andi Kleen <ak@...ux.intel.com>, namhyung@...nel.org,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org,
Arnaldo Carvalho de Melo <acme@...nel.org>
Subject: Re: [PATCH v5 0/8] perf report: Add latency and parallelism profiling
On Thu, Feb 6, 2025 at 10:41 AM Dmitry Vyukov <dvyukov@...gle.com> wrote:
> On Thu, 6 Feb 2025 at 19:30, Andi Kleen <ak@...ux.intel.com> wrote:
[snip]
> > We traditionally didn't do it, but in general test coverage
> > of perf report is too low, so I would recommend to add some simple
> > test case in the perf test scripts.
>
> What of this is testable within the current testing framework?
> Also how do I run tests? I failed to figure it out.
Often just having a test that ensure a command doesn't segfault is
progress :-) The shell tests Andi mentions are here:
https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git/tree/tools/perf/tests/shell?h=perf-tools-next
There's no explicit `perf report` test there but maybe the annotate,
diff or record tests could give you some ideas.
Thanks,
Ian
Powered by blists - more mailing lists