From: Tadhg Kearney <tadhg.kearney@intel.com>
To: dts@dpdk.org
Cc: reshma.pattan@intel.com, Tadhg Kearney <tadhg.kearney@intel.com>
Subject: [dts][V3 1/2] test_plans/*: Remove old DPDK RTE flags from power tests
Date: Tue, 29 Mar 2022 10:24:07 +0000 [thread overview]
Message-ID: <20220329102408.1137392-2-tadhg.kearney@intel.com> (raw)
In-Reply-To: <20220329102408.1137392-1-tadhg.kearney@intel.com>
Remove refernce to flags that don't exist anymore
Signed-off-by: Tadhg Kearney <tadhg.kearney@intel.com>
---
test_plans/power_branch_ratio_test_plan.rst | 5 ++---
test_plans/power_telemetry_test_plan.rst | 5 -----
2 files changed, 2 insertions(+), 8 deletions(-)
diff --git a/test_plans/power_branch_ratio_test_plan.rst b/test_plans/power_branch_ratio_test_plan.rst
index 4bbf95af..ba943693 100644
--- a/test_plans/power_branch_ratio_test_plan.rst
+++ b/test_plans/power_branch_ratio_test_plan.rst
@@ -47,9 +47,8 @@ Prepare work
intel_pstate=enable
-5. Set CONFIG_RTE_LIBRTE_POWER_DEBUG=y CONFIG_RTE_LIBRTE_POWER=y in /config/common_base file.
-6. modprobe msr module to let the application can get the CPU HW info.
-7. Let user space can control the CPU frequency::
+5. modprobe msr module to let the application can get the CPU HW info.
+6. Let user space can control the CPU frequency::
cpupower frequency-set -g userspace
diff --git a/test_plans/power_telemetry_test_plan.rst b/test_plans/power_telemetry_test_plan.rst
index 0afb0f77..8804129c 100644
--- a/test_plans/power_telemetry_test_plan.rst
+++ b/test_plans/power_telemetry_test_plan.rst
@@ -53,11 +53,6 @@ Preparation Work for Settings
cpupower frequency-set -g userspace
-Compile DPDK with telemetry enabled, enable telemetry lib in configuration file::
-
- -CONFIG_RTE_LIBRTE_TELEMETRY=n
- +CONFIG_RTE_LIBRTE_TELEMETRY=y
-
Test Case 1 : Check all 3 type of power related info reported by Telemetry System
=================================================================================
--
2.25.1
next prev parent reply other threads:[~2022-03-29 10:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 10:24 [dts][V3 0/2] Remove old DPDK " Tadhg Kearney
2022-03-29 10:24 ` Tadhg Kearney [this message]
2022-03-29 10:24 ` [dts][V3 2/2] tests/*: " Tadhg Kearney
2022-03-30 7:23 ` Dong, JunX
2022-03-31 6:31 ` lijuan.tu
2022-03-30 7:19 ` [dts][V3 0/2] " Dong, JunX
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=20220329102408.1137392-2-tadhg.kearney@intel.com \
--to=tadhg.kearney@intel.com \
--cc=dts@dpdk.org \
--cc=reshma.pattan@intel.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).