From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from relay.hostedemail.com (smtprelay0017.hostedemail.com [216.40.44.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 42C333A1E63; Mon, 29 Dec 2025 21:52:21 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=216.40.44.17 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1767045144; cv=none; b=lXdtCWYpOLpZoR4i8yoboSlTP5BvJpTkrMQCHmxiv+FfRrQmjq8qaViNWVNdEHH/72FiOhWIeC4aFQp+564DdA/4AIl1r9XnUhoZpR7DvcmHpcZkiU7AyZnvzOyGE4DURgZYOmEspeT3i4QXdWg4xFXT6s5pQJE9HLCwRNZ7Xiw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1767045144; c=relaxed/simple; bh=4ywAmQVU0G/pvYvKC9csakmwK7FDApBjH1KA53p9lz8=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=QLyORyfR2237l67xkB9luNiHuZhKOEGfG+DoFAGXajO9vFDsbyN6GqoZwB+eT9/0puVlqw4/ZFMslJ/7qq9wXUy/jXHlXhbt1ndbAsGXt3cuzJB2JVkgkwVKeDVwtKUo/Y3ccbWdUlLXI+2ROOH1vs0Vqm1LZjuFU25Y8f8oBb0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=goodmis.org; spf=pass smtp.mailfrom=goodmis.org; arc=none smtp.client-ip=216.40.44.17 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=goodmis.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=goodmis.org Received: from omf14.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay09.hostedemail.com (Postfix) with ESMTP id 7EF338C9FB; Mon, 29 Dec 2025 21:52:17 +0000 (UTC) Received: from [HIDDEN] (Authenticated sender: rostedt@goodmis.org) by omf14.hostedemail.com (Postfix) with ESMTPA id E3CAB30; Mon, 29 Dec 2025 21:52:06 +0000 (UTC) Date: Mon, 29 Dec 2025 16:52:12 -0500 From: Steven Rostedt To: "Rafael J. Wysocki" Cc: Christian Loehle , Samuel Wu , Huang Rui , "Gautham R. Shenoy" , Mario Limonciello , Perry Yuan , Jonathan Corbet , Viresh Kumar , Masami Hiramatsu , Mathieu Desnoyers , Srinivas Pandruvada , Len Brown , Alexei Starovoitov , Daniel Borkmann , Andrii Nakryiko , Martin KaFai Lau , Eduard Zingerman , Song Liu , Yonghong Song , John Fastabend , KP Singh , Stanislav Fomichev , Hao Luo , Jiri Olsa , Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo , Namhyung Kim , Mark Rutland , Alexander Shishkin , Ian Rogers , Adrian Hunter , James Clark , kernel-team@android.com, linux-pm@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org, bpf@vger.kernel.org, linux-perf-users@vger.kernel.org Subject: Re: [PATCH v3 1/2] cpufreq: Replace trace_cpu_frequency with trace_policy_frequency Message-ID: <20251229165212.5bd8508d@gandalf.local.home> In-Reply-To: References: <20251201202437.3750901-1-wusamuel@google.com> <20251201202437.3750901-2-wusamuel@google.com> <20251204114844.54953b01@gandalf.local.home> X-Mailer: Claws Mail 3.20.0git84 (GTK+ 2.24.33; x86_64-pc-linux-gnu) Precedence: bulk X-Mailing-List: linux-trace-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: E3CAB30 X-Stat-Signature: wceh78mpg7qfr393sy85h1jjj769oezy X-Rspamd-Server: rspamout05 X-Session-Marker: 726F737465647440676F6F646D69732E6F7267 X-Session-ID: U2FsdGVkX1+2hC1Yzk4ER7pLFvkZFUP4nb/X3Txx7bQ= X-HE-Tag: 1767045126-456558 X-HE-Meta: U2FsdGVkX18EZFLrqenngO/VKz57dSQljyE+X/DKPMolhiaAZdiq4Vdj/POhMfVCNA1v2UnrtNCySyoKeeFDLvKypXNU9MQrmExdybIHDGcgT9ZF9vVSHFW5sMC/RdNO03HxzIPWGhLsQBiZmN+bK3TWy4EPkbtQiKtRcjNqt7LDj6hIMOB7hXuiRoTg8bY1GKx18Q6CPXVaMWimem0/xdDPzzOF857I5p424BJvnPFmyjiZmGb8n+H3B/oa9N8q6Ub8zlacLYVWRIEaFMtPTRBRoRxSac6AzEieG33tgKLBJlgF5/bKl0XkhOzqoYTOzJgXeyn5dJa9a9qJM0eD2b9sJR1OrqJo On Thu, 4 Dec 2025 18:24:57 +0100 "Rafael J. Wysocki" 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