From: yufengmx <yufengx.mo@intel.com>
To: dts@dpdk.org, lei.a.yao@intel.com
Cc: yufengmx <yufengx.mo@intel.com>
Subject: [dts] [PATCH V4 0/4] vm_pw_mgmt_policy: upload suite test plan and script
Date: Tue, 24 Dec 2019 09:56:24 +0800 [thread overview]
Message-ID: <20191224015628.11931-1-yufengx.mo@intel.com> (raw)
A feature allows workload to deliver policy to the host to manage power controls
such as p-states extends the thinking of the current scheme moving away
from direct controls to policy controls to avoid latency & jitter
penalties. Also provides the ability to react faster.
v4:
- remove support architecture description.
-
v3:
- change turbo command execution result check condition.
- rebase source code.
-
v2:
- use new pktgen methods as traffic policy mode testing packet generator.
- abandon non-blocked ixia traffic source code changes in framework.
- add query script methods to take the place of non-blocked query method.
- use cpu turbo status query script method to take the place of local api call.
- change all functional test cases to performance test cases to be easier to deploy in one execution config.
- add power driver type check method.
- add cpupower tool existence check method.
- optimize cpu scaling_max_freq/scaling_available_frequencies/scaling_min_freq query time consumption.
- add cpu frequency preset method to clear previous testing influence.
- add vf passthrough to vm to do traffic policy testing.
yufengmx (4):
conf/vm_pw_mgmt_policy: virtual machine configuration
test_plans/vm_pw_mgmt_policy: add test plan index
test_plans/vm_pw_mgmt_policy: upload test plan
tests/vm_pw_mgmt_policy: upload automation script
conf/vm_pw_mgmt_policy.cfg | 30 +
test_plans/index.rst | 1 +
test_plans/vm_pw_mgmt_policy_test_plan.rst | 335 +++++++
tests/TestSuite_vm_pw_mgmt_policy.py | 994 +++++++++++++++++++++
4 files changed, 1360 insertions(+)
create mode 100644 conf/vm_pw_mgmt_policy.cfg
create mode 100644 test_plans/vm_pw_mgmt_policy_test_plan.rst
create mode 100644 tests/TestSuite_vm_pw_mgmt_policy.py
--
2.21.0
next reply other threads:[~2019-12-24 1:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-24 1:56 yufengmx [this message]
2019-12-24 1:56 ` [dts] [PATCH V4 1/4] conf/vm_pw_mgmt_policy: virtual machine configuration yufengmx
2019-12-24 1:55 ` Yao, Lei A
2019-12-24 1:56 ` [dts] [PATCH V4 2/4] test_plans/vm_pw_mgmt_policy: add test plan index yufengmx
2019-12-24 1:55 ` Yao, Lei A
2019-12-24 1:56 ` [dts] [PATCH V4 3/4] test_plans/vm_pw_mgmt_policy: upload test plan yufengmx
2019-12-24 1:56 ` Yao, Lei A
2019-12-24 1:56 ` [dts] [PATCH V4 4/4] tests/vm_pw_mgmt_policy: upload automation script yufengmx
2019-12-24 1:56 ` Yao, Lei A
2019-12-27 6:29 ` [dts] [PATCH V4 0/4] vm_pw_mgmt_policy: upload suite test plan and script 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=20191224015628.11931-1-yufengx.mo@intel.com \
--to=yufengx.mo@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).