From: Swapnil Sapkal <swapnil.sapkal@amd.com>
To: <ray.huang@amd.com>, <shuah@kernel.org>
Cc: <sukrut.bellary@gmail.com>, <li.meng@amd.com>,
<gautham.shenoy@amd.com>, <wyes.karny@amd.com>,
<Perry.Yuan@amd.com>, <Mario.Limonciello@amd.com>,
<linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-kselftest@vger.kernel.org>,
Swapnil Sapkal <swapnil.sapkal@amd.com>
Subject: [PATCH v3 0/2] Fix issues observed in selftests/amd-pstate
Date: Tue, 3 Oct 2023 05:10:04 +0000 [thread overview]
Message-ID: <20231003051006.6343-1-swapnil.sapkal@amd.com> (raw)
This series fixes issues observed with selftests/amd-pstate while
running performance comparison tests with different governors. First
patch changes relative paths with absolute path and also change it
with correct path wherever it is broken.
The second patch adds an option to provide perf binary path to
handle the case where distro perf does not work.
Changelog v2->v3:
* Split the patch into two patches
Swapnil Sapkal (2):
selftests/amd-pstate: Fix broken paths to run workloads in amd-pstate-ut
selftests/amd-pstate: Added option to provide perf binary path
.../x86/amd_pstate_tracer/amd_pstate_trace.py | 2 +-
.../testing/selftests/amd-pstate/gitsource.sh | 14 +++++++----
tools/testing/selftests/amd-pstate/run.sh | 23 +++++++++++++------
tools/testing/selftests/amd-pstate/tbench.sh | 4 ++--
4 files changed, 28 insertions(+), 15 deletions(-)
--
2.34.1
next reply other threads:[~2023-10-03 5:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 5:10 Swapnil Sapkal [this message]
2023-10-03 5:10 ` [PATCH v3 1/2] selftests/amd-pstate: Fix broken paths to run workloads in amd-pstate-ut Swapnil Sapkal
2023-10-06 19:05 ` Mario Limonciello
2023-10-12 5:00 ` Swapnil Sapkal
2023-10-03 5:10 ` [PATCH v3 2/2] selftests/amd-pstate: Added option to provide perf binary path Swapnil Sapkal
2023-10-06 18:59 ` Mario Limonciello
2023-10-12 5:04 ` Swapnil Sapkal
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=20231003051006.6343-1-swapnil.sapkal@amd.com \
--to=swapnil.sapkal@amd.com \
--cc=Mario.Limonciello@amd.com \
--cc=Perry.Yuan@amd.com \
--cc=gautham.shenoy@amd.com \
--cc=li.meng@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=ray.huang@amd.com \
--cc=shuah@kernel.org \
--cc=sukrut.bellary@gmail.com \
--cc=wyes.karny@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
all inboxes | Powered by JetHome®