[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <175346932935.1444596.3621368930739538107.b4-ty@kernel.org>
Date: Fri, 25 Jul 2025 11:48:49 -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>,
Jean-Philippe Romain <jean-philippe.romain@...s.st.com>,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org,
Ian Rogers <irogers@...gle.com>
Subject: Re: [PATCH v1] perf pfm: Don't force loading of all PMUs
On Mon, 21 Jul 2025 18:34:49 -0700, Ian Rogers wrote:
> Force loading all PMUs adds significant cost because DRM and other
> PMUs are loaded, it should also not be required if the pmus__
> functions are used.
>
> Tested by run perf test, in particular the pfm related tests. Also
> `perf list` is identical before and after.
>
> [...]
Applied to perf-tools-next, thanks!
Best regards,
Namhyung
Powered by blists - more mailing lists