From: lihong <lihongx.ma@intel.com>
To: dts@dpdk.org
Cc: lei.a.yao@intel.com, lihong <lihongx.ma@intel.com>
Subject: [dts] [PATCH V1] test_plan: add test plan of power pstate
Date: Tue, 8 Oct 2019 02:38:17 +0800 [thread overview]
Message-ID: <1570473497-3935-1-git-send-email-lihongx.ma@intel.com> (raw)
Signed-off-by: lihong <lihongx.ma@intel.com>
---
test_plans/power_pstate_test_plan.rst | 97 +++++++++++++++++++++++++++++++++++
1 file changed, 97 insertions(+)
create mode 100644 test_plans/power_pstate_test_plan.rst
diff --git a/test_plans/power_pstate_test_plan.rst b/test_plans/power_pstate_test_plan.rst
new file mode 100644
index 0000000..f2a5e19
--- /dev/null
+++ b/test_plans/power_pstate_test_plan.rst
@@ -0,0 +1,97 @@
+.. Copyright (c) <2019>, Intel Corporation
+ All rights reserved.
+
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions
+ are met:
+
+ - Redistributions of source code must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+
+ - Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in
+ the documentation and/or other materials provided with the
+ distribution.
+
+ - Neither the name of Intel Corporation nor the names of its
+ contributors may be used to endorse or promote products derived
+ from this software without specific prior written permission.
+
+ THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+ "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+ LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
+ FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
+ COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
+ INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+ (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+ SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+ HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+ STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+ ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
+ OF THE POSSIBILITY OF SUCH DAMAGE.
+
+=======================================
+Power Lib Based on Intel Pstate Driver
+=======================================
+Before DPDK 19.02 version, DPDK power lib is based on acpi-cpufreq driver in Linux.
+From DPDK 19.02, Power lib start support intel_pstate driver.
+
+Prepare Settings
+================
+1. Turn on Speedstep option in BIOS
+2. Turn on CPU C3 and C6
+3. Turn on Turbo in BIOS
+4. In BIOS set up the HWPM to "Native Mode"
+5. Turn off "Hyper Threading"
+6. Probe msr (used to get Intel CPU's no_turbo max frequency)
+
+Definition of CPU frequency in this test suite:
+sys_min = sys/devices/system/cpu/cpu{}/cpufreq/cpuinfo_min_freq
+sys_max = sys/devices/system/cpu/cpu{}/cpufreq/cpuinfo_max_freq
+no_turbo_max = [rdmsr -p 1 0x0CE -f 15:8 -d]00000
+
+Note:
+For Intel Processor, If "Hyper Threading" enabled in BIOS, need change frequency on both HT core
+at the same time to let the frequency take effect.
+From DPDK 19.08, vm_power_manager will set fifo channel for each core.
+Before DPDK 19.08, all core will share 1 fifo channel
+
+Test Case1 : Test Pstate lib basic action based on directly power command
+===========================================================================
+Step 1. Create powermonitor fold for::
+
+ Create monitor channel folder, /tmp/powermonitor, give permission for read and write
+
+Step 2. Luanch VM power manager sample::
+
+ ./examples/vm_power_manager/build/vm_power_mgr -l 1-4 -n 4 --file-prefix=power --no-pci
+
+Step 3. Prepare different command in JSON format then send it to the fifo channel::
+
+ The command Sample as following:
+ {"instruction": {
+ "name": "policy",
+ "command": "power",
+ "unit": "SCALE_MAX"
+ }}
+
+ Test with following 6 command type with following Sequency:
+ ENABLE_TURBO -> SCALE_MIN -> SCALE_MAX -> DISABLE_TURBO -> ENABLE_TURBO -> SCALE_UP -> SCALE_DOWN
+ cat command.json >/tmp/powermonitor/fifo{core_number}
+ :"SCALE_MAX": Scale frequency of this core to maximum
+ :"SCALE_MIN": Scale frequency of this core to minimum
+ :"SCALE_UP": Scale up frequency of this core
+ :"SCALE_DOWN": Scale down frequency of this core
+ :"ENABLE_TURBO": Enable Turbo Boost for this core
+ :"DISABLE_TURBO": Disable Turbo Boost for this core
+
+Step 4. Check the Core1 frequency for each command in Step 3::
+
+ min=sys/devices/system/cpu/cpu{}/cpufreq/scaling_min_freq
+ max=sys/devices/system/cpu/cpu{}/cpufreq/scaling_max_freq
+ Check point of Step SCALE_MIN: min=max=sys_min
+ Check point of Step SCALE_MAX: min=max=sys_max
+ Check point of Step DISABLE_TURBO: min=max=no_turbo_max
+ Check point of Step ENABLE_TURBO: min=max=no_turbo_max
+ Check point of Step SCALE_UP: min=max=sys_max
+ Check point of Step SCALE_DOWN: min=max=no_turbo_max
--
2.7.4
next reply other threads:[~2019-10-08 2:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 18:38 lihong [this message]
2019-10-09 7:56 ` Yao, Lei A
2019-10-12 5:54 ` Tu, Lijuan
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=1570473497-3935-1-git-send-email-lihongx.ma@intel.com \
--to=lihongx.ma@intel.com \
--cc=dts@dpdk.org \
--cc=lei.a.yao@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).