From: Tadhg Kearney <tadhg.kearney@intel.com>
To: reshma.pattan@intel.com
Cc: dts@dpdk.org, Tadhg Kearney <tadhg.kearney@intel.com>
Subject: [dts][PATCH 1/2] test_plans/vm_power_manager_test_plans: remove multivm test
Date: Fri, 25 Feb 2022 12:49:28 +0000 [thread overview]
Message-ID: <20220225124929.674983-2-tadhg.kearney@intel.com> (raw)
In-Reply-To: <20220225124929.674983-1-tadhg.kearney@intel.com>
Signed-off-by: Tadhg Kearney <tadhg.kearney@intel.com>
---
test_plans/vm_power_manager_test_plan.rst | 25 -----------------------
1 file changed, 25 deletions(-)
diff --git a/test_plans/vm_power_manager_test_plan.rst b/test_plans/vm_power_manager_test_plan.rst
index f297e818..cc78998b 100644
--- a/test_plans/vm_power_manager_test_plan.rst
+++ b/test_plans/vm_power_manager_test_plan.rst
@@ -233,28 +233,3 @@ Test Case 6: VM Scale CPU Frequency to Max
4. Check other CPUs' frequency is not affected by change above
5. check if the other VM works fine (if they use different CPUs)
-Test Case 7: VM Power Management Multi VMs
-==========================================
-1. Setup VM power management environment for VM1
-2. Setup VM power management environment for VM2
-3. Run power-manager in Host::
-
- x86_64-native-linuxapp-gcc/examples/dpdk-guest_cli -c 0x3 -n 4
-
-4. Startup VM1 and VM2
-5. Add VM1 in host and check vm_power_mgr can get frequency normally::
-
- vmpower> add_vm <vm1_name>
- vmpower> add_channels <vm1_name> all
- vmpower> show_cpu_freq <core_num>
-
-6. Add VM2 in host and check vm_power_mgr can get frequency normally::
-
- vmpower> add_vm <vm2_name>
- vmpower> add_channels <vm2_name> all
- vmpower> show_cpu_freq <core_num>
-
-7. Run Case3-6 and check VM1 and VM2 cpu frequency can by modified by guest_cli
-8. Poweroff VM2 and remove VM2 from host vm_power_mgr::
-
- vmpower> rm_vm <vm2_name>
--
2.25.1
--------------------------------------------------------------
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263
This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.
next prev parent reply other threads:[~2022-02-25 12:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 12:49 [dts][PATCH 0/2] remove multivms test case Tadhg Kearney
2022-02-25 12:49 ` Tadhg Kearney [this message]
2022-02-25 12:49 ` [dts][PATCH 2/2] conf/vm_power_manager: remove vm1 info Tadhg Kearney
2022-02-27 14:14 ` 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=20220225124929.674983-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).