[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174232093806.2542685.5490063295095338711.b4-ty@kernel.org>
Date: Tue, 18 Mar 2025 11:02:18 -0700
From: Namhyung Kim <namhyung@...nel.org>
To: Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>, Adrian Hunter <adrian.hunter@...el.com>,
Kan Liang <kan.liang@...ux.intel.com>,
Thomas Richter <tmricht@...ux.ibm.com>,
James Clark <james.clark@...aro.org>, linux-perf-users@...r.kernel.org,
linux-kernel@...r.kernel.org, Ian Rogers <irogers@...gle.com>
Subject: Re: [PATCH v1] perf tests annotate: Add pipe output to output
testing
On Tue, 11 Mar 2025 14:16:35 -0700, Ian Rogers wrote:
> Parameterize the basic testing to generate directly a perf.data file
> or to generate/use one from pipe input or output. To simplify the
> refactor move some of the head/grep logic around. Use "-q" with grep
> to make the test output cleaner.
>
>
Applied to perf-tools-next, thanks!
Best regards,
Namhyung
Powered by blists - more mailing lists