[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9178149c-45e8-3de4-58db-b8b8d27b3a08@linux.intel.com>
Date: Thu, 18 May 2023 13:45:06 -0400
From: "Liang, Kan" <kan.liang@...ux.intel.com>
To: Arnaldo Carvalho de Melo <acme@...nel.org>,
James Clark <james.clark@....com>,
Ian Rogers <irogers@...gle.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>,
Namhyung Kim <namhyung@...nel.org>,
Adrian Hunter <adrian.hunter@...el.com>,
Thomas Richter <tmricht@...ux.ibm.com>,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 1/2] perf test attr: Update no event/metric
expectations
Hi Arnaldo,
On 2023-05-18 8:55 a.m., Liang, Kan wrote:
> On 2023-05-18 8:20 a.m., Arnaldo Carvalho de Melo wrote:
>> Em Thu, May 18, 2023 at 08:50:14AM +0100, James Clark escreveu:
>>>
>>> On 17/05/2023 23:57, Ian Rogers wrote:
>>>> Previously hard coded events/metrics were used, update for the use of
>>>> the TopdownL1 json metric group.
>>>>
>>>> Fixes: 94b1a603fca7 ("perf stat: Add TopdownL1 metric as a default if present")
>>>> Signed-off-by: Ian Rogers <irogers@...gle.com>
>>>> ---
>>>> tools/perf/tests/attr/base-stat | 2 +-
>>>> tools/perf/tests/attr/test-stat-default | 80 ++++++++-----
>>>> tools/perf/tests/attr/test-stat-detailed-1 | 95 +++++++++------
>>>> tools/perf/tests/attr/test-stat-detailed-2 | 119 +++++++++++--------
>>>> tools/perf/tests/attr/test-stat-detailed-3 | 127 ++++++++++++---------
>>>> 5 files changed, 249 insertions(+), 174 deletions(-)
>>>>
>>> Reviewed-by: James Clark <james.clark@....com>
>> Thanks, applied both patches to perf-tools.
>>
> Could you please hold patch 1 for a while?
Sorry for the noise.
Ian has addressed my concerns. The patch looks good to me now.
It also fixes a "Failed" on my Cascade Lake machine.
Tested-by: Kan Liang <kan.liang@...ux.intel.com>
But for long term, we probably need a better solution to avoid keeping
adding such non-architectural events in the test case.
Thanks,
Kan
Powered by blists - more mailing lists