[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251229165212.5bd8508d@gandalf.local.home>
Date: Mon, 29 Dec 2025 16:52:12 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: "Rafael J. Wysocki" <rafael@...nel.org>
Cc: Christian Loehle <christian.loehle@....com>, Samuel Wu
<wusamuel@...gle.com>, Huang Rui <ray.huang@....com>, "Gautham R. Shenoy"
<gautham.shenoy@....com>, Mario Limonciello <mario.limonciello@....com>,
Perry Yuan <perry.yuan@....com>, Jonathan Corbet <corbet@....net>, Viresh
Kumar <viresh.kumar@...aro.org>, Masami Hiramatsu <mhiramat@...nel.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>, Srinivas Pandruvada
<srinivas.pandruvada@...ux.intel.com>, Len Brown <lenb@...nel.org>, Alexei
Starovoitov <ast@...nel.org>, Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andrii@...nel.org>, Martin KaFai Lau
<martin.lau@...ux.dev>, Eduard Zingerman <eddyz87@...il.com>, Song Liu
<song@...nel.org>, Yonghong Song <yonghong.song@...ux.dev>, John Fastabend
<john.fastabend@...il.com>, KP Singh <kpsingh@...nel.org>, Stanislav
Fomichev <sdf@...ichev.me>, Hao Luo <haoluo@...gle.com>, Jiri Olsa
<jolsa@...nel.org>, Peter Zijlstra <peterz@...radead.org>, Ingo Molnar
<mingo@...hat.com>, Arnaldo Carvalho de Melo <acme@...nel.org>, Namhyung
Kim <namhyung@...nel.org>, Mark Rutland <mark.rutland@....com>, Alexander
Shishkin <alexander.shishkin@...ux.intel.com>, Ian Rogers
<irogers@...gle.com>, Adrian Hunter <adrian.hunter@...el.com>, James Clark
<james.clark@...aro.org>, kernel-team@...roid.com,
linux-pm@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
bpf@...r.kernel.org, linux-perf-users@...r.kernel.org
Subject: Re: [PATCH v3 1/2] cpufreq: Replace trace_cpu_frequency with
trace_policy_frequency
On Thu, 4 Dec 2025 18:24:57 +0100
"Rafael J. Wysocki" <rafael@...nel.org> wrote:
> My concern is that the patch effectively removes one trace point
> (cpu_frequency) and adds another one with a different format
> (policy_frequency), updates one utility in the kernel tree and expects
> everyone else to somehow know that they should switch over.
>
> I know about at least several people who have their own scripts using
> this tracepoint though.
Hi Rafael,
Can you reach out to those that have scripts that use this trace event to
see if it can be changed?
Thanks,
-- Steve
Powered by blists - more mailing lists