From: Jinzhou Su <Jinzhou.Su@amd.com>
To: <rjw@rjwysocki.net>, <linux-pm@vger.kernel.org>,
<srinivas.pandruvada@linux.intel.com>, <dsmythies@telus.net>
Cc: <ray.huang@amd.com>, <viresh.kumar@linaro.org>,
<todd.e.brandt@linux.intel.com>, <linux-kernel@vger.kernel.org>,
<deepak.sharma@amd.com>, <alexander.deucher@amd.com>,
<xiaojian.du@amd.com>, <perry.yuan@amd.com>, <li.meng@amd.com>,
<jinzhou.su@amd.com>, Jinzhou Su <Jinzhou.Su@amd.com>
Subject: [PATCH V2 4/4] Documentation: amd-pstate: add tracer tool introduction
Date: Fri, 4 Mar 2022 14:07:24 +0800 [thread overview]
Message-ID: <20220304060724.314582-5-Jinzhou.Su@amd.com> (raw)
In-Reply-To: <20220304060724.314582-1-Jinzhou.Su@amd.com>
Add amd pstate tracer tool introduction
Signed-off-by: Jinzhou Su <Jinzhou.Su@amd.com>
---
Documentation/admin-guide/pm/amd-pstate.rst | 26 +++++++++++++++++++++
1 file changed, 26 insertions(+)
diff --git a/Documentation/admin-guide/pm/amd-pstate.rst b/Documentation/admin-guide/pm/amd-pstate.rst
index 2f066df4ee9c..17dd7396e8fc 100644
--- a/Documentation/admin-guide/pm/amd-pstate.rst
+++ b/Documentation/admin-guide/pm/amd-pstate.rst
@@ -369,6 +369,32 @@ governor (for the policies it is attached to), or by the ``CPUFreq`` core (for t
policies with other scaling governors).
+Tracer Tool
+-------------
+
+``amd_pstate_tracer.py`` can record and parse amd-pstate trace log, then
+generate performance plots. This utility can be used to debug and tune the
+performance of the amd-pstate driver. The tracer tool needs to import intel
+pstate tracer.
+
+Tracer tool located in linux/tools/power/x86/amd_pstate_tracer. It can be
+used in two ways. If trace file is available, then directly parse the file
+with command ::
+
+ ./amd_pstate_trace.py [-c cpus] -t <trace_file> -n <test_name>
+
+Or generate trace file with root privilege, then parse and plot with command ::
+
+ sudo ./amd_pstate_trace.py [-c cpus] -n <test_name> -i <interval> [-m kbytes]
+
+The test result can be found in ``results/test_name``. Following is the example
+about part of the output. ::
+
+ common_cpu common_secs common_usecs min_perf des_perf max_perf freq mperf apef tsc load duration_ms sample_num elapsed_time common_comm
+ CPU_005 712 116384 39 49 166 0.7565 9645075 2214891 38431470 25.1 11.646 469 2.496 kworker/5:0-40
+ CPU_006 712 116408 39 49 166 0.6769 8950227 1839034 37192089 24.06 11.272 470 2.496 kworker/6:0-1264
+
+
Reference
===========
--
2.27.0
next prev parent reply other threads:[~2022-03-04 6:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 6:07 [PATCH V2 0/4] Add tracer tool for AMD P-State driver Jinzhou Su
2022-03-04 6:07 ` [PATCH V2 1/4] cpufreq: amd-pstate: Add more tracepoint for AMD P-State module Jinzhou Su
2022-03-04 6:42 ` Huang Rui
2022-03-04 18:49 ` Rafael J. Wysocki
2022-03-07 2:53 ` Huang Rui
2022-03-09 1:23 ` Su, Jinzhou (Joe)
2022-03-09 13:29 ` Huang Rui
2022-03-04 6:07 ` [PATCH V2 2/4] tools/power/x86/intel_pstate_tracer: make tracer as a module Jinzhou Su
2022-03-04 6:44 ` Huang Rui
2022-03-04 6:07 ` [PATCH V2 3/4] tools/power/x86/amd_pstate_tracer: Add tracer tool for AMD P-state Jinzhou Su
2022-03-04 6:48 ` Huang Rui
2022-03-04 6:07 ` Jinzhou Su [this message]
2022-03-04 6:56 ` [PATCH V2 4/4] Documentation: amd-pstate: add tracer tool introduction Huang Rui
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220304060724.314582-5-Jinzhou.Su@amd.com \
--to=jinzhou.su@amd.com \
--cc=alexander.deucher@amd.com \
--cc=deepak.sharma@amd.com \
--cc=dsmythies@telus.net \
--cc=li.meng@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=perry.yuan@amd.com \
--cc=ray.huang@amd.com \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=todd.e.brandt@linux.intel.com \
--cc=viresh.kumar@linaro.org \
--cc=xiaojian.du@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).