Patch Detail
get:
Show a patch.
patch:
Update a patch.
put:
Update a patch.
GET /api/patches/108519/?format=api
{ "id": 108519, "url": "http://patches.dpdk.org/api/patches/108519/?format=api", "web_url": "http://patches.dpdk.org/project/dts/patch/20220303143600.826855-1-tadhg.kearney@intel.com/", "project": { "id": 3, "url": "http://patches.dpdk.org/api/projects/3/?format=api", "name": "DTS", "link_name": "dts", "list_id": "dts.dpdk.org", "list_email": "dts@dpdk.org", "web_url": "", "scm_url": "git://dpdk.org/tools/dts", "webscm_url": "http://git.dpdk.org/tools/dts/", "list_archive_url": "https://inbox.dpdk.org/dts", "list_archive_url_format": "https://inbox.dpdk.org/dts/{}", "commit_url_format": "" }, "msgid": "<20220303143600.826855-1-tadhg.kearney@intel.com>", "list_archive_url": "https://inbox.dpdk.org/dts/20220303143600.826855-1-tadhg.kearney@intel.com", "date": "2022-03-03T14:36:00", "name": "[V3] test_plans/*: modify power test plans to adapt meson build", "commit_ref": null, "pull_url": null, "state": "accepted", "archived": false, "hash": "7347302321f5e0227d5954fccf679311271dcd35", "submitter": { "id": 2533, "url": "http://patches.dpdk.org/api/people/2533/?format=api", "name": "Tadhg Kearney", "email": "tadhg.kearney@intel.com" }, "delegate": null, "mbox": "http://patches.dpdk.org/project/dts/patch/20220303143600.826855-1-tadhg.kearney@intel.com/mbox/", "series": [ { "id": 22005, "url": "http://patches.dpdk.org/api/series/22005/?format=api", "web_url": "http://patches.dpdk.org/project/dts/list/?series=22005", "date": "2022-03-03T14:36:00", "name": "[V3] test_plans/*: modify power test plans to adapt meson build", "version": 3, "mbox": "http://patches.dpdk.org/series/22005/mbox/" } ], "comments": "http://patches.dpdk.org/api/patches/108519/comments/", "check": "warning", "checks": "http://patches.dpdk.org/api/patches/108519/checks/", "tags": {}, "related": [], "headers": { "Return-Path": "<dts-bounces@dpdk.org>", "X-Original-To": "patchwork@inbox.dpdk.org", "Delivered-To": "patchwork@inbox.dpdk.org", "Received": [ "from mails.dpdk.org (mails.dpdk.org [217.70.189.124])\n\tby inbox.dpdk.org (Postfix) with ESMTP id 712C4A0351;\n\tThu, 3 Mar 2022 15:36:07 +0100 (CET)", "from [217.70.189.124] (localhost [127.0.0.1])\n\tby mails.dpdk.org (Postfix) with ESMTP id 40BF24276B;\n\tThu, 3 Mar 2022 15:36:07 +0100 (CET)", "from mga01.intel.com (mga01.intel.com [192.55.52.88])\n by mails.dpdk.org (Postfix) with ESMTP id ECE4540687\n for <dts@dpdk.org>; Thu, 3 Mar 2022 15:36:04 +0100 (CET)", "from orsmga002.jf.intel.com ([10.7.209.21])\n by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384;\n 03 Mar 2022 06:36:03 -0800", "from silpixa00401183.ir.intel.com ([10.55.129.105])\n by orsmga002.jf.intel.com with ESMTP; 03 Mar 2022 06:36:02 -0800" ], "DKIM-Signature": "v=1; a=rsa-sha256; c=relaxed/simple;\n d=intel.com; i=@intel.com; q=dns/txt; s=Intel;\n t=1646318165; x=1677854165;\n h=from:to:cc:subject:date:message-id;\n bh=Uc+6uXJuirvE0ELz1tLQWImVcWMQnKe5gWI83WirJSQ=;\n b=ght0G4P0jR59IHt2ovMbfENAk2ivW+efIScRhAt9cOxYiViqzg6ukxZO\n IZwOB6r0PMIlVeIs+yTABsc8f1oipDV9APJIm8SSg/FmQNqjYbb1n5YiC\n S6AOfMkMkjFkPf+KeyIwg1ThRBBuGKEG83DoLBdyylJDw3JPeCv5h3LKP\n tDNh+agL+XkExWpKlMkp0T2+2vDrsPDlHwSczTQ5/yCqLFj0AQkgSVZaj\n XiUOR217cDq4THdWtfix09LdHYPlAXg4DMy86aZzaRimLsfsDhRx+Fk0Z\n b7b9Y84CJnFM7OpRoQ/rSn4jrw5xrPVV74inIfUYj2g/qLY5tbf+n6zby w==;", "X-IronPort-AV": [ "E=McAfee;i=\"6200,9189,10274\"; a=\"278371515\"", "E=Sophos;i=\"5.90,151,1643702400\"; d=\"scan'208\";a=\"278371515\"", "E=Sophos;i=\"5.90,151,1643702400\"; d=\"scan'208\";a=\"508611647\"" ], "Content-Type": "multipart/mixed; boundary=\"===============3223145280527744169==\"", "MIME-Version": [ "1.0", "1.0" ], "X-ExtLoop1": "1", "From": "Tadhg Kearney <tadhg.kearney@intel.com>", "To": "dts@dpdk.org", "Cc": "reshma.pattan@intel.com,\n\tTadhg Kearney <tadhg.kearney@intel.com>", "Subject": "[dts][V3] test_plans/*: modify power test plans to adapt meson build", "Date": "Thu, 3 Mar 2022 14:36:00 +0000", "Message-Id": "<20220303143600.826855-1-tadhg.kearney@intel.com>", "X-Mailer": "git-send-email 2.25.1", "X-BeenThere": "dts@dpdk.org", "X-Mailman-Version": "2.1.29", "Precedence": "list", "List-Id": "test suite reviews and discussions <dts.dpdk.org>", "List-Unsubscribe": "<https://mails.dpdk.org/options/dts>,\n <mailto:dts-request@dpdk.org?subject=unsubscribe>", "List-Archive": "<http://mails.dpdk.org/archives/dts/>", "List-Post": "<mailto:dts@dpdk.org>", "List-Help": "<mailto:dts-request@dpdk.org?subject=help>", "List-Subscribe": "<https://mails.dpdk.org/listinfo/dts>,\n <mailto:dts-request@dpdk.org?subject=subscribe>", "Errors-To": "dts-bounces@dpdk.org" }, "content": "Signed-off-by: Tadhg Kearney <tadhg.kearney@intel.com>\n---\n .../power_bidirection_channel_test_plan.rst | 16 ++++-----\n test_plans/power_branch_ratio_test_plan.rst | 6 ++--\n test_plans/power_empty_poll_test_plan.rst | 4 +--\n test_plans/power_negative_test_plan.rst | 30 ++++++++--------\n test_plans/power_pbf_test_plan.rst | 8 ++---\n test_plans/power_pstate_test_plan.rst | 4 +--\n test_plans/power_telemetry_test_plan.rst | 2 +-\n test_plans/vm_power_manager_test_plan.rst | 14 ++++----\n test_plans/vm_pw_mgmt_policy_test_plan.rst | 36 ++++++++++---------\n 9 files changed, 62 insertions(+), 58 deletions(-)", "diff": "diff --git a/test_plans/power_bidirection_channel_test_plan.rst b/test_plans/power_bidirection_channel_test_plan.rst\nindex a6df6597..319c0a75 100644\n--- a/test_plans/power_bidirection_channel_test_plan.rst\n+++ b/test_plans/power_bidirection_channel_test_plan.rst\n@@ -59,7 +59,7 @@ Step 1. Launch VM using libvirt::\n \n Step 2. Launch VM power manager example on the host to monitor the channel from VM::\n \n- ./examples/vm_power_manager/build/vm_power_mgr -c 0xfffe -n 4 --no-pci\n+ ./<build_target>/examples/dpdk-vm_power_manager -c 0xfffe -n 4 --no-pci\n vmpower> add_vm [vm name]\n vmpower> add_channels [vm name] all\n vmpower> set_channel_status [vm name] all enabled\n@@ -71,9 +71,9 @@ Step 2. Launch VM power manager example on the host to monitor the channel from\n vmpower> set_channel_status ubuntu all enabled\n vmpower> show_vm ubuntu\n \n-Step 3. In the VM, launch guest_vm_power_mgr to set and send the power manager policy to the host power example::\n+Step 3. In the VM, launch dpdk-guest_cli to set and send the power manager policy to the host power example::\n \n- ./examples/vm_power_manager/guest_cli/build/guest_vm_power_mgr -c 0xfe -n 4 -m 1024 --no-pci --file-prefix=vm_power -- --vm-name=ubuntu --vcpu-list=0-7\n+ ./<build_target>/examples/dpdk-guest_cli -c 0xfe -n 4 -m 1024 --no-pci --file-prefix=vm_power -- --vm-name=ubuntu --vcpu-list=0-7\n \n Send command to the core 7 on host APP:\n vmpower(guest)> set_cpu_freq 7 down\n@@ -100,14 +100,14 @@ Step 1. Launch VM using libvirt::\n \n Step 2. Launch VM power manager example on the host to monitor the channel from VM::\n \n- ./examples/vm_power_manager/build/vm_power_mgr -c 0xfffe -n 4 --no-pci\n+ ./<build_target>/examples/dpdk-vm_power_manager -c 0xfffe -n 4 --no-pci\n vmpower> add_vm [vm name]\n vmpower> add_channels [vm name] all\n vmpower> set_channel_status [vm name] all enabled\n vmpower> show_vm [vm name]\n vmpower> set_query <vm_name> <enable|disable>\n \n-Step 3. Enable the query permission for target VM from host vm_power_mgr example::\n+Step 3. Enable the query permission for target VM from host dpdk-vm_power_manager example::\n \n Command format: set_query <vm_name> <enable|disable>\n if vm name is ubuntu,command as following:\n@@ -115,7 +115,7 @@ Step 3. Enable the query permission for target VM from host vm_power_mgr example\n \n Step 4. Query the CPU frequency for all CPU cores from VM side::\n \n- ./examples/vm_power_manager/guest_cli/build/guest_vm_power_mgr -c 0xfe -n 4 -m 1024 --no-pci --file-prefix=vm_power -- --vm-name=ubuntu --vcpu-list=0-7\n+ ./<build_target>/examples/dpdk-guest_cli -c 0xfe -n 4 -m 1024 --no-pci --file-prefix=vm_power -- --vm-name=ubuntu --vcpu-list=0-7\n vmpower> query_cpu_freq <core_num> | all\n \n Check vcpu 0~7 frequency info will be returned, for example:\n@@ -130,7 +130,7 @@ Step 4. Query the CPU frequency for all CPU cores from VM side::\n \n Step 5. Disable query permission from VM, check the host CPU frequency won't be returned::\n \n- at host side, disable query permission by vm_power_mgr example:\n+ at host side, disable query permission by dpdk-vm_power_manager example:\n vmpower> set_query ubuntu disable\n \n at VM side, query CPU frequency again, this action should not be executed successfully, log as following:\n@@ -164,7 +164,7 @@ Step 5: Query CPU capability for core out of scope, check no CPU info will be re\n \n Step 6: Disable query permission from VM, check the host CPU capability won't be returned::\n \n- at host side, disable query permission by vm_power_mgr example:\n+ at host side, disable query permission by dpdk-vm_power_manager example:\n vmpower> set_query ubuntu disable\n \n at VM side, query CPU capability again, this action should not be executed successfully, log as following:\ndiff --git a/test_plans/power_branch_ratio_test_plan.rst b/test_plans/power_branch_ratio_test_plan.rst\nindex daecc133..4bbf95af 100644\n--- a/test_plans/power_branch_ratio_test_plan.rst\n+++ b/test_plans/power_branch_ratio_test_plan.rst\n@@ -58,17 +58,17 @@ no_turbo_max=$(rdmsr -p 2 0x0CE -f 15:8 -d)00000\n \n Test Case 1 : Set Branch-Ratio Test Rate by User ====================================================================================\n 1. Launch VM power manager sample on the host to run branch monitor.\n-./x86_64-native-linuxapp-gcc/examples/dpdk-vm_power_manager -v -c 0xe -n 1 -m 1024 --no-pci -- --core-branch-ratio=1-3:0.3\n+./<build_target>/examples/dpdk-vm_power_manager -v -c 0xe -n 1 -m 1024 --no-pci -- --core-branch-ratio=1-3:0.3\n \n 2. Launch testpmd with fwd io mode::\n \n- ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -v -c 0x6 -n 1 -m 1024 --file-prefix=vmpower2 -- -i\n+ ./<build_target>/app/dpdk-testpmd -v -c 0x6 -n 1 -m 1024 --file-prefix=vmpower2 -- -i\n > start\n \n 3. Inject packet with packet generator to the NIC, with line rate,\n check the branch ratio and the related CPU frequency, in this case, the\n core 2 will be used by testpmd as worker core, branch ratio will be shown as\n-following in vm_power_mgr's log output::\n+following in dpdk-vm_power_manager's log output::\n \n 1: 0.0048 {250065} {20001}\n 0: 0.0307 {35782} {20000}\ndiff --git a/test_plans/power_empty_poll_test_plan.rst b/test_plans/power_empty_poll_test_plan.rst\nindex 44728308..f18a483a 100644\n--- a/test_plans/power_empty_poll_test_plan.rst\n+++ b/test_plans/power_empty_poll_test_plan.rst\n@@ -124,7 +124,7 @@ Test Case1 : Basic Training mode test based on one NIC with l3fwd-power\n =======================================================================\n Step 1. Bind One NIC to DPDK driver, launch l3fwd-power with empty-poll enabled\n \n- ./l3fwd-power -l 1-2 -n 4 -- -p 0x1 -P --config=\"(0,0,2)\" --empty-poll=\"1,0,0\" -l 10 -m 6 -h 1\n+ ./<build_target>/examples/dpdk-l3fwd-power -l 1-2 -n 4 -- -p 0x1 -P --config=\"(0,0,2)\" --empty-poll=\"1,0,0\" -l 10 -m 6 -h 1\n \n Step 2. Check the log also when changing the inject packet rate as following:\n \n@@ -139,6 +139,6 @@ Test Case2: No-Training mode test based on one NIC with l3fwd-power\n ===================================================================\n Step 1. Bind One NIC to DPDK driver, launch l3fwd-power with empty-poll enabled\n \n- ./l3fwd-power -l 1-2 -n 4 -- -p 0x1 -P --config=\"(0,0,2)\" --empty-poll=\"0,350000,500000\" -l 10 -m 6 -h 1\n+ ./<build_target>/examples/dpdk-l3fwd-power -l 1-2 -n 4 -- -p 0x1 -P --config=\"(0,0,2)\" --empty-poll=\"0,350000,500000\" -l 10 -m 6 -h 1\n \n Step 2. Check no training steps are executed in sample's launch log.\ndiff --git a/test_plans/power_negative_test_plan.rst b/test_plans/power_negative_test_plan.rst\nindex bf2cfebf..1ca7e1ef 100644\n--- a/test_plans/power_negative_test_plan.rst\n+++ b/test_plans/power_negative_test_plan.rst\n@@ -46,18 +46,18 @@ Preparation work\n \n Test Case1: Inject Malformed JSON Command file to fifo channel\n ===============================================================\n-Step 1. Create powermonitor fold for vm_power_manager sample::\n+Step 1. Create powermonitor fold for dpdk-vm_power_manager sample::\n \n mkdir /tmp/powermonitor\n chmod 777 /tmp/powermonitor\n \n Step 2. Luanch VM power manager sample::\n \n- ./x86_64-native-linuxapp-gcc/examples/dpdk-vm_power_manager -l 1-3 -n 4 --file-prefix=test1 --no-pci\n+ ./<build_target>/examples/dpdk-vm_power_manager -l 1-3 -n 4 --file-prefix=test1 --no-pci\n \n Step 3. Prepare policy in JSON format then send it to the fifo channel:\n Prepare different command in JSON format then send it to the fifo channel\n- Modify \"name\", \"resource_id\", \"command\" to large character string to check if the vm_power_mgr sample will crash\n+ Modify \"name\", \"resource_id\", \"command\" to large character string to check if the dpdk-vm_power_manager sample will crash\n For example::\n \n {\"policy\": {\n@@ -71,20 +71,20 @@ Step 4. Send Json format command to the fifo channel::\n \n cat command.json > /tmp/powermonitor/fifo22\n \n-Check point: no crash at the vm_power_mgr application side.\n+Check point: no crash at the dpdk-vm_power_manager application side.\n \n Potential issue: no warning for the user for the name too long, now is char[32], but no crash as strlcpy is uesed\n \n Test Case2: Send invalid command through JSON channel\n ======================================================\n-Step 1. Create powermonitor fold for vm_power_manager sample::\n+Step 1. Create powermonitor fold for dpdk-vm_power_manager sample::\n \n mkdir /tmp/powermonitor\n chmod 777 /tmp/powermonitor\n \n Step 2. Luanch VM power manager sample::\n \n- ./x86_64-native-linuxapp-gcc/examples/dpdk-vm_power_manager -l 1-3 -n 4 --file-prefix=test1 --no-pci\n+ ./<build_target>/examples/dpdk-vm_power_manager -l 1-3 -n 4 --file-prefix=test1 --no-pci\n \n Step 3. Prepare policy in JSON format then send it to the fifo channel:\n \n@@ -118,22 +118,22 @@ Note: For the VM xml file which will be used for creating the VM, it can re-use\n \n Step 2. Luanch VM power manager sample on the host to monitor the channel from VM::\n \n- ./x86_64-native-linuxapp-gcc/examples/dpdk-vm_power_manager -l 12-14 -n 4 --no-pci\n+ ./<build_taget>/examples/dpdk-vm_power_manager -l 12-14 -n 4 --no-pci\n > add_vm [vm name]\n > add_channels [vm name] all\n > set_channel_status [vm name] all enabled\n > show_vm [vm name]\n \n- Check the invalid input command for vm_power_mgr sample::\n+ Check the invalid input command for dpdk-vm_power_manager sample::\n \n > add_channels ubuntu 128\n > add_channel ubuntu 10000000000000000\n \n-Check point: No crash should be occur at vm_power_mgr sample\n+Check point: No crash should be occur at dpdk-vm_power_manager sample\n \n-Step 3. In the VM, launch guest_vm_power_mgr to set and send the power manager policy to the host power sample::\n+Step 3. In the VM, launch dpdk-guest_cli to set and send the power manager policy to the host power sample::\n \n- ./x86_64-native-linuxapp-gcc/examples/dpdk-guest_cli -c 0xff -n 4 -m 1024 --no-pci --file-prefix=yaolei \\\n+ ./<build_target>/examples/dpdk-guest_cli -c 0xff -n 4 -m 1024 --no-pci --file-prefix=yaolei \\\n -- --vm-name=ubuntu --vcpu-list=0-7\n > set_cpu_freq 128 down\n > set_cpu_freq 1000000000000 down\n@@ -146,14 +146,14 @@ Step 3. In the VM, launch guest_vm_power_mgr to set and send the power manager p\n \n Test Case4: TRAFFIC Policy Test based on JSON configure file with large integer number\n ========================================================================================\n-Step 1. Generate 1 VF under vfio-pci driver, launch vm_power_mgr sample with PF, for example::\n+Step 1. Generate 1 VF under vfio-pci driver, launch dpdk-vm_power_manager sample with PF, for example::\n \n echo 1 > /sys/bus/pci/drivers/vfio-pci/0000\\:82\\:00.0/max_vfs\n- ./x86_64-native-linuxapp-gcc/examples/dpdk-vm_power_manager -l 1-4 -n 4 --socket-mem=1024,1024 --file-prefix=test1 -a 82:00.0 -- -p 0x01\n+ ./<build_target>/examples/dpdk-vm_power_manager -l 1-4 -n 4 --socket-mem=1024,1024 --file-prefix=test1 -a 82:00.0 -- -p 0x01\n \n Step 2. Launch testpmd with VF::\n \n- ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 5-6 -n 4 --socket-mem=1024,1024 --file-prefix=test2 -a 0000:82:02.0 -- -i\n+ ./<build_target>/app/dpdk-testpmd -l 5-6 -n 4 --socket-mem=1024,1024 --file-prefix=test2 -a 0000:82:02.0 -- -i\n > set fwd macswap\n > start\n \n@@ -172,4 +172,4 @@ Step 4. Send Json format command to the fifo channel::\n \n cat traffic.json > /tmp/powermonitor/fifo6\n \n-Check point: No crash should be occur at vm_power_mgr sample\n+Check point: No crash should be occur at dpdk-vm_power_manager sample\ndiff --git a/test_plans/power_pbf_test_plan.rst b/test_plans/power_pbf_test_plan.rst\nindex 6a38fc61..ad8ea1f2 100644\n--- a/test_plans/power_pbf_test_plan.rst\n+++ b/test_plans/power_pbf_test_plan.rst\n@@ -59,7 +59,7 @@ Step 1. Create powermonitor fold for::\n \n Step 2. Compile DPDK with Power Lib debug info on, then Luanch VM power manager sample::\n \n- ./examples/vm_power_manager/build/vm_power_mgr -l 1-46 -n 4 --file-prefix=power --no-pci\n+ ./<build_target>/examples/dpdk-vm_power_manager -l 1-46 -n 4 --file-prefix=power --no-pci\n \n Check two different base_max frequency will be shown in log, for example on Intel 6230N Processor:\n The log will be like as following\n@@ -87,7 +87,7 @@ Step 1. Create powermonitor fold for::\n \n Step 2. Compile DPDK with Power Lib debug info on, then aunch VM power manager sample::\n \n- ./examples/vm_power_manager/build/vm_power_mgr -l 1-46 -n 4 --file-prefix=power --no-pci\n+ ./<build_target>/examples/dpdk-vm_power_manager -l 1-46 -n 4 --file-prefix=power --no-pci\n \n Step 3. Prepare different command in JSON format::\n \n@@ -102,7 +102,7 @@ Step 3. Prepare different command in JSON format::\n Step 4: Send different command to power sample, then check the frequency::\n \n Command Steps: ENABLE_TURBO-> SCALE_MAX-> SCALE_DOWN-> SCALE_MIN\n- Send action JSON file to vm_power_mgr's fifo channel, each core will have it's own channel:\n+ Send action JSON file to dpdk-vm_power_manager's fifo channel, each core will have it's own channel:\n cat command.json >/tmp/powermonitor/fifo{core_number}\n \n Check the CPU frequency is changed accordingly in previous list by following method:\n@@ -129,7 +129,7 @@ Step 1. Create powermonitor fold for::\n \n Step 2. Compile DPDK with Power Lib debug info on, then launch VM power manager sample::\n \n- ./examples/vm_power_manager/build/vm_power_mgr -l 1-46 -n 4 --file-prefix=power --no-pci\n+ ./<build_target>/examples/dpdk-vm_power_manager -l 1-46 -n 4 --file-prefix=power --no-pci\n \n Step 3. Prepare Several command in JSON format then send it to the fifo channel for the high priority core::\n \ndiff --git a/test_plans/power_pstate_test_plan.rst b/test_plans/power_pstate_test_plan.rst\nindex f2a5e199..7bdd43b6 100644\n--- a/test_plans/power_pstate_test_plan.rst\n+++ b/test_plans/power_pstate_test_plan.rst\n@@ -53,7 +53,7 @@ no_turbo_max = [rdmsr -p 1 0x0CE -f 15:8 -d]00000\n Note:\n For Intel Processor, If \"Hyper Threading\" enabled in BIOS, need change frequency on both HT core\n at the same time to let the frequency take effect.\n-From DPDK 19.08, vm_power_manager will set fifo channel for each core.\n+From DPDK 19.08, dpdk-vm_power_manager will set fifo channel for each core.\n Before DPDK 19.08, all core will share 1 fifo channel\n \n Test Case1 : Test Pstate lib basic action based on directly power command\n@@ -64,7 +64,7 @@ Step 1. Create powermonitor fold for::\n \n Step 2. Luanch VM power manager sample::\n \n- ./examples/vm_power_manager/build/vm_power_mgr -l 1-4 -n 4 --file-prefix=power --no-pci\n+ ./<build_target>/examples/dpdk-vm_power_manager -l 1-4 -n 4 --file-prefix=power --no-pci\n \n Step 3. Prepare different command in JSON format then send it to the fifo channel::\n \ndiff --git a/test_plans/power_telemetry_test_plan.rst b/test_plans/power_telemetry_test_plan.rst\nindex fd27f8a1..0afb0f77 100644\n--- a/test_plans/power_telemetry_test_plan.rst\n+++ b/test_plans/power_telemetry_test_plan.rst\n@@ -63,7 +63,7 @@ Test Case 1 : Check all 3 type of power related info reported by Telemetry Syste\n =================================================================================\n 1. Launch l3fwd-power sample with telemetry enabled, bind one NIC to DPDK driver, launch l3fwd-power::\n \n- ./l3fwd-power -l 1-2 -n 4 --telemetry -- -p 0x1 -P --config=\"(0,0,2)\" --telemetry\n+ ./<build_target>/examples/dpdk-l3fwd-power -l 1-2 -n 4 --telemetry -- -p 0x1 -P --config=\"(0,0,2)\" --telemetry\n \n 2. Get the telemetry info using dpdk-telemetry-client.py script, then choose mode 3 ``Send for global Metrics``::\n \ndiff --git a/test_plans/vm_power_manager_test_plan.rst b/test_plans/vm_power_manager_test_plan.rst\nindex cc78998b..f85d2ef9 100644\n--- a/test_plans/vm_power_manager_test_plan.rst\n+++ b/test_plans/vm_power_manager_test_plan.rst\n@@ -121,15 +121,15 @@ Test Case 1: VM Power Management Channel\n <address type='virtio-serial' controller='0' bus='0' port='4'/>\n </channel>\n \n-3. Run power-manager in Host::\n+3. Run dpdk-guest_cli in Host::\n \n- x86_64-native-linuxapp-gcc/examples/dpdk-guest_cli -c 0x3 -n 4\n+ ./<build_target>/examples/dpdk-guest_cli -c 0x3 -n 4\n \n-4. Startup VM and run guest_vm_power_mgr::\n+4. Startup VM and run dpdk-guest_cli::\n \n- x86_64-native-linuxapp-gcc/examples/dpdk-guest_cli -c 0x1f -n 4 -- -i\n+ ./<build_target>/examples/dpdk-guest_cli -c 0x1f -n 4 -- -i\n \n-5. Add vm in host and check vm_power_mgr can get frequency normally::\n+5. Add vm in host and check dpdk-vm_power_manager can get frequency normally::\n \n vmpower> add_vm <vm_name>\n vmpower> add_channels <vm_name> all\n@@ -153,9 +153,9 @@ Test Case 1: VM Power Management Channel\n [3]: Physical CPU Mask 0x10\n [4]: Physical CPU Mask 0x20\n \n-7. Run vm_power_mgr in vm::\n+7. Run dpdk-guest_cli in vm::\n \n- x86_64-native-linuxapp-gcc/examples/dpdk-guest_cli -c 0x1f -n 4\n+ ./<build_target>/examples/dpdk-guest_cli -c 0x1f -n 4\n \n Check monitor channel for all cores has been connected.\n \ndiff --git a/test_plans/vm_pw_mgmt_policy_test_plan.rst b/test_plans/vm_pw_mgmt_policy_test_plan.rst\nindex 98894ff5..4237583f 100644\n--- a/test_plans/vm_pw_mgmt_policy_test_plan.rst\n+++ b/test_plans/vm_pw_mgmt_policy_test_plan.rst\n@@ -168,11 +168,13 @@ Set up testing environment\n \n #. Compile and run power-manager in host, core number should >= 3, add vm in host.\n \n- export RTE_SDK=`pwd`\n- export RTE_TARGET=x86_64-native-linuxapp-gcc\n- make -C examples/vm_power_manager\n+ CC=gcc meson -Denable_kmods=True -Dlibdir=lib --default-library=static <build_target>\n+ ninja -C <build_target>\n \n- ./examples/vm_power_manager/build/vm_power_mgr -c 0xffff -n 4\n+ meson configure -Dexamples=vm_power_manager <build_target>\n+ ninja -C <build_target>\n+\n+ ./<build_target>/examples/dpdk-vm_power_manager -c 0xffff -n 4\n \n vmpower> add_vm <vm_name>\n vmpower> add_channels <vm_name> all\n@@ -181,20 +183,22 @@ Set up testing environment\n #. Run testpmd on vm0 when do traffic policy testing, other test cases ignore\n this step.\n \n- ./testpmd -c 0x3 -n 1 -v -m 1024 --file-prefix=vmpower1 -- -i --port-topology=loop\n+ ./<build_target>/app/dpdk-testpmd -c 0x3 -n 1 -v -m 1024 --file-prefix=vmpower1 -- -i --port-topology=loop\n \n testpmd> set fwd mac\n testpmd> set promisc all on\n testpmd> port start all\n testpmd> start\n \n-#. Compile and run guest_vm_power_mgr on VM.\n+#. Compile and run dpdk-guest_cli on VM.\n+\n+ CC=gcc meson -Denable_kmods=True -Dlibdir=lib --default-library=static <build_target>\n+ ninja -C <build_target>\n \n- export RTE_SDK=`pwd`\n- export RTE_TARGET=x86_64-native-linuxapp-gcc\n- make -C examples/vm_power_manager/guest_cli\n+ meson configure -Dexamples=vm_power_manager/guest_cli <build_target>\n+ ninja -C <build_target>\n \n- ./examples/vm_power_manager/guest_cli/build/guest_vm_power_mgr \\\n+ ./<build_target>/examples/dpdk-guest_cli \\\n -c 0xff -n 4 --file-prefix=vmpower2 -- -i --vm-name=<vm name> \\\n --policy=<policy name> --vcpu-list=<vcpus list> --busy-hours=<time stage>\n \n@@ -227,7 +231,7 @@ check these content.\n #. when dut clock is set to a desired busy hours, put core to max freq.\n #. when dut clock is set to a desired quiet hours, put core to min freq.\n \n-This case test multiple guest_vm_power_mgr options, they are composited\n+This case test multiple dpdk-guest_cli options, they are composited\n by these content as below::\n \n #. --policy\n@@ -252,7 +256,7 @@ steps:\n \n #. set up testing environment refer to ``Set up testing environment`` steps.\n \n-#. trigger policy on vm DUT from guest_vm_power_mgr console::\n+#. trigger policy on vm DUT from dpdk-guest_cli console::\n \n vmpower(guest)> send_policy now\n \n@@ -269,7 +273,7 @@ vcpus frequency will run at med frequency.\n #. use packet generator to send a stream with a pps rate less than 1800000,\n vcpu frequency will run at min frequency.\n \n-This case test multiple guest_vm_power_mgr options, they are composited\n+This case test multiple dpdk-guest_cli options, they are composited\n by these content as below::\n \n #. --policy\n@@ -288,7 +292,7 @@ steps:\n \n #. set up testing environment refer to ``Set up testing environment`` steps.\n \n-#. trigger policy on vm DUT from guest_vm_power_mgr console::\n+#. trigger policy on vm DUT from dpdk-guest_cli console::\n \n vmpower(guest)> send_policy now\n \n@@ -306,7 +310,7 @@ steps:\n \n #. set up testing environment refer to ``Set up testing environment`` steps.\n \n-#. set cpu turbo disable on vm DUT from guest_vm_power_mgr console::\n+#. set cpu turbo disable on vm DUT from dpdk-guest_cli console::\n \n vmpower(guest)> set_cpu_freq <core_num> disable_turbo\n \n@@ -324,7 +328,7 @@ steps:\n \n #. set up testing environment refer to ``Set up testing environment`` steps.\n \n-#. set cpu turbo enable on vm DUT from guest_vm_power_mgr console::\n+#. set cpu turbo enable on vm DUT from dpdk-guest_cli console::\n \n vmpower(guest)> set_cpu_freq <vm_core_num> enable_turbo\n \n", "prefixes": [ "V3" ] }