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 0/4] Add tracer tool for AMD P-State driver
Date: Fri, 4 Mar 2022 14:07:20 +0800 [thread overview]
Message-ID: <20220304060724.314582-1-Jinzhou.Su@amd.com> (raw)
Hello,
intel_pstate_tracer is a useful tool to analyze the performance of
intel_pstate driver. We upstream out AMD P-state driver into Linux
kernel recently and like to use similar tool to tune the performance
of the driver.
I modified intel_pstate_tracer.py then it could import as a module to
analyze AMD P-State trace event. Other trace event also can benifit from
this change once they need this tool.
intel_pstate_tracer could be used as the same way as before and the
original functionality isn't broken.
Changes from V1->V2
-Add tracer documentation in amd-pstate RST
-fix typo in amd_pstate_trace.py
-add "Co-developed-by" in patch 1/4
Thanks,
Joe
Jinzhou Su (4):
cpufreq: amd-pstate: Add more tracepoint for AMD P-State module
tools/power/x86/intel_pstate_tracer: make tracer as a module
tools/power/x86/amd_pstate_tracer: Add tracer tool for AMD P-state
Documentation: amd-pstate: add tracer tool introduction
Documentation/admin-guide/pm/amd-pstate.rst | 26 ++
MAINTAINERS | 1 +
drivers/cpufreq/amd-pstate-trace.h | 22 +-
drivers/cpufreq/amd-pstate.c | 59 ++-
.../x86/amd_pstate_tracer/amd_pstate_trace.py | 354 ++++++++++++++++++
.../intel_pstate_tracer.py | 260 +++++++------
6 files changed, 588 insertions(+), 134 deletions(-)
create mode 100755 tools/power/x86/amd_pstate_tracer/amd_pstate_trace.py
--
2.27.0
next reply other threads:[~2022-03-04 6:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 6:07 Jinzhou Su [this message]
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 ` [PATCH V2 4/4] Documentation: amd-pstate: add tracer tool introduction Jinzhou Su
2022-03-04 6:56 ` 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-1-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).