Re: [dts] [dts 10/28] add unit_test_power rst file into dts

["Liu, Yong" <yong.liu@intel.com>]

Haifeng, some small comments below.

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of TangHaifeng
> Sent: Tuesday, May 26, 2015 3:36 PM
> To: dts@dpdk.org
> Cc: Fu, JingguoX
> Subject: [dts] [dts 10/28] add unit_test_power rst file into dts
> 
> ---
>  test_plans/unit_tests_power_test_plan.rst |   80
> +++++++++++++++++++++++++++++
>  1 files changed, 80 insertions(+), 0 deletions(-)
>  create mode 100644 test_plans/unit_tests_power_test_plan.rst
> 
> diff --git a/test_plans/unit_tests_power_test_plan.rst
> b/test_plans/unit_tests_power_test_plan.rst
> new file mode 100644
> index 0000000..9e42444
> --- /dev/null
> +++ b/test_plans/unit_tests_power_test_plan.rst
> @@ -0,0 +1,80 @@
> +.. Copyright (c) <2010>, Intel Corporation

Please take care of the date should be 2015.

> +   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 Autotests
> +===============
> +
> +This is the test plan for the Intel® DPDK Power library.
> +
> +Description
> +===========
> +
> +This section explains how to run the unit tests for Power features. The
> test
> +can be launched independently using the command line interface.
> +This test is implemented as a linuxapp environment application.
> +
> +The complete test suite is launched automatically using a python-expect
> +script (launched using ``make test``) that sends commands to
> +the application and checks the results. A test report is displayed on
> +stdout.
> +
> +The steps to run the unit test manually are as follow::
> +
> +
> +  # make -C ./app/test/
> +  # ./app/test/test -n 1 -c ffff
> +  RTE>> power_autotest
> +
> +
> +The final output of the test has to be "Test OK"
> +
> +==================
> +ACPI CPU Frequency
> +==================
> +

I remember ACPI autotest request speedStep feature on in BIOS.
Please add prerequisites of this case. 

    - Enable Enhanced Intel SpeedStep(R) Tech
    - Enable Processor C3
    - Enable Processor C6

> +This section explains how to run the unit tests for Power features. The
> test
> +can be launched independently using the command line interface.
> +This test is implemented as a linuxapp environment application.
> +
> +The complete test suite is launched automatically using a python-expect
> +script (launched using ``make test``) that sends commands to
> +the application and checks the results. A test report is displayed on
> +stdout.
> +
> +The steps to run the unit test manually are as follow::
> +
> +  # make -C ./app/test/
> +  # ./app/test/test -n 1 -c ffff
> +  RTE>> power_acpi_cpufreq_autotest
> +
> +The final output of the test has to be "Test OK"
> --
> 1.7.4.4