[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ca386344-cd1e-4667-b21e-318680f6cff3@linaro.org>
Date: Mon, 14 Oct 2024 09:42:15 +0100
From: James Clark <james.clark@...aro.org>
To: Arnaldo Carvalho de Melo <acme@...nel.org>,
Namhyung Kim <namhyung@...nel.org>
Cc: Ingo Molnar <mingo@...nel.org>, Thomas Gleixner <tglx@...utronix.de>,
Jiri Olsa <jolsa@...nel.org>, Ian Rogers <irogers@...gle.com>,
Adrian Hunter <adrian.hunter@...el.com>,
Kan Liang <kan.liang@...ux.intel.com>, Clark Williams <williams@...hat.com>,
linux-kernel@...r.kernel.org, linux-perf-users@...r.kernel.org,
Arnaldo Carvalho de Melo <acme@...hat.com>
Subject: Re: [PATCH v2 0/3] Document the 'perf test -w' workloads
functionality
On 11/10/2024 6:14 pm, Arnaldo Carvalho de Melo wrote:
> From: Arnaldo Carvalho de Melo <acme@...hat.com>
>
> Hi,
>
> I noticed that the 'perf test -w' code wasn't well exposed, so
> add a '-w --list' option to list the existing workloads and document it
> in the 'perf test' man page.
>
> - Arnaldo
>
> v2:
>
> - Use --list-workloads, as suggesed by James Clark.
>
> - Add info in the man page about the parameters the built-in workloads
> accept.
>
> Arnaldo Carvalho de Melo (3):
> perf test: Introduce workloads__for_each()
> perf test: Introduce '-w --list' to list the available workloads
> perf test: Document the -w/--workload option
>
> tools/perf/Documentation/perf-test.txt | 14 +++++++++++++
> tools/perf/tests/builtin-test.c | 27 ++++++++++++++++++++++----
> 2 files changed, 37 insertions(+), 4 deletions(-)
>
With the fix for the comment on patch 3:
Reviewed-by: James Clark <james.clark@...aro.org>
Powered by blists - more mailing lists