From nobody Mon Feb 9 05:59:11 2026 Received: from mail-pg1-f202.google.com (mail-pg1-f202.google.com [209.85.215.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 201C92773EE for ; Mon, 1 Dec 2025 20:24:52 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.215.202 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764620693; cv=none; b=GnVvfc76GDghtlRa+zt02vrGsKj3PtjSI4EHnAa/HdkTK0Yy9bbuTlR4kaWsnP9ckS5TdrUgywA+n/13ChelGmemYQFXBhBPrSyxsyLZZ64DziSK4Ty6ydSCyZ+tK5400nkw+qKpYDK3BZ1mKlmC8aehFGqbdYhvAqy1EOVOWvs= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764620693; c=relaxed/simple; bh=9VtX2NvFz0RoQVJ8SSqGMuTYPnLO3r9LWpqks/kmpMQ=; h=Date:In-Reply-To:Mime-Version:References:Message-ID:Subject:From: To:Cc:Content-Type; b=T4/ApNtevTUFoyWjOCeESFg4i3bzlzDd0eHK38EwRbVndq+muov7bC+SMkP015C1ax2MAn3/+HwPkY+0afxHBEqRd1RdoYGxX7CvlM+kT1+ZdRO2M2oVMs63f0Pu2XQLw05awTpx5gEjLYifJPPBj/5TtKSVbCxdPrdbumc7y3U= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=google.com; spf=pass smtp.mailfrom=flex--wusamuel.bounces.google.com; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b=jkNbt3ou; arc=none smtp.client-ip=209.85.215.202 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=google.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=flex--wusamuel.bounces.google.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="jkNbt3ou" Received: by mail-pg1-f202.google.com with SMTP id 41be03b00d2f7-bde2e654286so3723825a12.3 for ; Mon, 01 Dec 2025 12:24:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20230601; t=1764620691; x=1765225491; darn=vger.kernel.org; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:from:to:cc:subject:date:message-id:reply-to; bh=iuYJ8a9yf5YfCIOX0vDCxkx5Zc9d0WA0EbWHTfFbCpI=; b=jkNbt3ouuc6NmxFq5apXPbnMYpm1+zjWpeLCHENUhZshBHu5HtyWtBRrtrgDl7yalQ OtXQasM1U+p8W2X/IYCa2cUExCHo0oVWoB8FJsSl1BeopyHbTrYz+9YzTGuqlAKYUaQI IJapEgCG+EizpaCFsG6l5ATwt5rzAJ4+tDTdFaxXAEItPwJu0MKHQ7YGAErlkZb1XXhU MWgjhSmcDoofFGwbkjtHo5nMbpLoUUNjN5loYr7jv9kC3Q+I/88Ak23hMapuj4HFYfBO son19Lz+dHz87y71srH8WwtEHospUet67m9ZKRWT2Iyh2vFf+e/JVNXH8Z5jFwFJqBQ3 1TiQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1764620691; x=1765225491; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=iuYJ8a9yf5YfCIOX0vDCxkx5Zc9d0WA0EbWHTfFbCpI=; b=ub8G8+K7DvQYNGtJrDb0e2M34UnVmAtRxJTJjZ12amC/Ur9jBgWb+jcHwk5SIyoiys KQxzQbu83TrltJaorQ77xUbQJ/caFgjbTB/0ajbSqGY/zLaVI1Nij++PlQYD1Ue3mmIj /Gu1PgUNjMC61qz6zGUV1ZLKbdulxf7qUfpp5MxNpswK9VbDqlGwclTAmgEQmm23ExVZ 8CP9/AQIstH/UWxC8MzU99/zeZJp3r+fpqjgp4q9l1E/PLybf1IEAGdsAHLg/PkZeX+q wuVGkcN37RsuPN0aKXdrPCL+N1E3P92W02q1Djde5JY6OYNsAVvQbeqyej1pn4B2Ubhh IiXQ== X-Forwarded-Encrypted: i=1; AJvYcCXRq7k1T+lLwsENvbDWZ6udPrmbFHg1hw+hwvZbxuHYEh6iVLNDttnEaiKY78EhNmESDfeCVx448fJbjKI=@vger.kernel.org X-Gm-Message-State: AOJu0YwDa9ocbnZM891gv7zHRA2aV1R5sCfEnySui2j0of3Q9Vsx2UQA q9J/iY7z6ikmFlH6ZR/dnkk21sYu9zMgbiD050WFDgSOD2kSqVWeLxDRXFjk/Qhdx4g43/hvSE5 gr2adRZhWJy8Deg== X-Google-Smtp-Source: AGHT+IGsvk85QlzW667SyDst19B1vMCsdIZFkhsIWO+5Oz5JLmlMK/v87N6vvqpae9OjXI/Z5iDlf2o2nXomaQ== X-Received: from dlbdd25.prod.google.com ([2002:a05:7022:a99:b0:11c:58e4:e325]) (user=wusamuel job=prod-delivery.src-stubby-dispatcher) by 2002:a05:7022:6726:b0:119:e56b:98ab with SMTP id a92af1059eb24-11cb3ede9dcmr19616669c88.18.1764620691371; Mon, 01 Dec 2025 12:24:51 -0800 (PST) Date: Mon, 1 Dec 2025 12:24:35 -0800 In-Reply-To: <20251201202437.3750901-1-wusamuel@google.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 References: <20251201202437.3750901-1-wusamuel@google.com> X-Mailer: git-send-email 2.52.0.107.ga0afd4fd5b-goog Message-ID: <20251201202437.3750901-3-wusamuel@google.com> Subject: [PATCH v3 2/2] cpufreq: Documentation update for trace_policy_frequency From: Samuel Wu To: Huang Rui , "Gautham R. Shenoy" , Mario Limonciello , Perry Yuan , Jonathan Corbet , "Rafael J. Wysocki" , Viresh Kumar , Steven Rostedt , 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 Cc: christian.loehle@arm.com, Samuel Wu , 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 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Documentation update corresponding to replace the cpu_frequency trace event with the policy_frequency trace event. Signed-off-by: Samuel Wu --- Documentation/admin-guide/pm/amd-pstate.rst | 10 +++++----- Documentation/admin-guide/pm/intel_pstate.rst | 14 +++++++------- Documentation/trace/events-power.rst | 2 +- 3 files changed, 13 insertions(+), 13 deletions(-) diff --git a/Documentation/admin-guide/pm/amd-pstate.rst b/Documentation/ad= min-guide/pm/amd-pstate.rst index e1771f2225d5..e110854ece88 100644 --- a/Documentation/admin-guide/pm/amd-pstate.rst +++ b/Documentation/admin-guide/pm/amd-pstate.rst @@ -503,8 +503,8 @@ Trace Events -------------- =20 There are two static trace events that can be used for ``amd-pstate`` -diagnostics. One of them is the ``cpu_frequency`` trace event generally us= ed -by ``CPUFreq``, and the other one is the ``amd_pstate_perf`` trace event +diagnostics. One of them is the ``policy_frequency`` trace event generally +used by ``CPUFreq``, and the other one is the ``amd_pstate_perf`` trace ev= ent specific to ``amd-pstate``. The following sequence of shell commands can be used to enable them and see their output (if the kernel is configured to support event tracing). :: @@ -531,9 +531,9 @@ configured to support event tracing). :: -0 [003] d.s.. 4995.980971: amd_pstate_perf: amd_mi= n_perf=3D85 amd_des_perf=3D85 amd_max_perf=3D166 cpu_id=3D3 changed=3Dfalse= fast_switch=3Dtrue -0 [011] d.s.. 4995.980996: amd_pstate_perf: amd_mi= n_perf=3D85 amd_des_perf=3D85 amd_max_perf=3D166 cpu_id=3D11 changed=3Dfals= e fast_switch=3Dtrue =20 -The ``cpu_frequency`` trace event will be triggered either by the ``schedu= til`` scaling -governor (for the policies it is attached to), or by the ``CPUFreq`` core = (for the -policies with other scaling governors). +The ``policy_frequency`` trace event will be triggered either by the +``schedutil`` scaling governor (for the policies it is attached to), or by= the +``CPUFreq`` core (for the policies with other scaling governors). =20 =20 Tracer Tool diff --git a/Documentation/admin-guide/pm/intel_pstate.rst b/Documentation/= admin-guide/pm/intel_pstate.rst index fde967b0c2e0..274c9208f342 100644 --- a/Documentation/admin-guide/pm/intel_pstate.rst +++ b/Documentation/admin-guide/pm/intel_pstate.rst @@ -822,23 +822,23 @@ Trace Events ------------ =20 There are two static trace events that can be used for ``intel_pstate`` -diagnostics. One of them is the ``cpu_frequency`` trace event generally u= sed -by ``CPUFreq``, and the other one is the ``pstate_sample`` trace event spe= cific -to ``intel_pstate``. Both of them are triggered by ``intel_pstate`` only = if -it works in the :ref:`active mode `. +diagnostics. One of them is the ``policy_frequency`` trace event generally +used by ``CPUFreq``, and the other one is the ``pstate_sample`` trace event +specific to ``intel_pstate``. Both of them are triggered by ``intel_pstat= e`` +only if it works in the :ref:`active mode `. =20 The following sequence of shell commands can be used to enable them and see their output (if the kernel is generally configured to support event traci= ng):: =20 # cd /sys/kernel/tracing/ # echo 1 > events/power/pstate_sample/enable - # echo 1 > events/power/cpu_frequency/enable + # echo 1 > events/power/policy_frequency/enable # cat trace gnome-terminal--4510 [001] ..s. 1177.680733: pstate_sample: core_busy= =3D107 scaled=3D94 from=3D26 to=3D26 mperf=3D1143818 aperf=3D1230607 tsc=3D= 29838618 freq=3D2474476 - cat-5235 [002] ..s. 1177.681723: cpu_frequency: state=3D2900000 cpu_id= =3D2 + cat-5235 [002] ..s. 1177.681723: policy_frequency: state=3D2900000 cpu_= id=3D2 policy_cpus=3D04 =20 If ``intel_pstate`` works in the :ref:`passive mode `, the -``cpu_frequency`` trace event will be triggered either by the ``schedutil`` +``policy_frequency`` trace event will be triggered either by the ``schedut= il`` scaling governor (for the policies it is attached to), or by the ``CPUFreq= `` core (for the policies with other scaling governors). =20 diff --git a/Documentation/trace/events-power.rst b/Documentation/trace/eve= nts-power.rst index f45bf11fa88d..f013c74b932f 100644 --- a/Documentation/trace/events-power.rst +++ b/Documentation/trace/events-power.rst @@ -26,8 +26,8 @@ cpufreq. :: =20 cpu_idle "state=3D%lu cpu_id=3D%lu" - cpu_frequency "state=3D%lu cpu_id=3D%lu" cpu_frequency_limits "min=3D%lu max=3D%lu cpu_id=3D%lu" + policy_frequency "state=3D%lu cpu_id=3D%lu policy_cpus=3D%*pb" =20 A suspend event is used to indicate the system going in and out of the suspend mode: --=20 2.52.0.107.ga0afd4fd5b-goog