From patchwork Fri Feb 25 12:49:28 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Tadhg Kearney X-Patchwork-Id: 108354 Return-Path: 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]) by inbox.dpdk.org (Postfix) with ESMTP id 27243A034C; Fri, 25 Feb 2022 13:49:55 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 1E97E41160; Fri, 25 Feb 2022 13:49:55 +0100 (CET) Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by mails.dpdk.org (Postfix) with ESMTP id 240DC4068B for ; Fri, 25 Feb 2022 13:49:52 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1645793393; x=1677329393; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=NDQ2pOAPs5lq+3QXoyfN3mOqFXc7GhvzcknxDdvSsC4=; b=lOShxlZTu+xV1Kdo8ykMAvOyoKP/HUqKcl3s2BfqqaIPUsTi6mhoSf89 UVf+UR1IhBVUTZv1vYRCA576rzUYqGG00ayI1a+72Ut837oGbT0Au2Fxa qAr+jP9UtQlszS9mCCxEu/1IKjRi9D/reAe+R1t/1cxWJIgxb9Z5zZSCh m4VLC/w8Gb4g0IWQ4JPALxs6X5ehzoZL+mB067JPiN2m7SiXryM5ZXPim yrLiT0wbYn4JXdPYV0ebushrXiutvRMAVYY0GFITq/X+QZTpNc0yRMoLg +8RyIe7LgHUHMziJc+GpaJPoJW6MaAWH+Kn+XoKZOJzTtw757qKYwyGs+ A==; X-IronPort-AV: E=McAfee;i="6200,9189,10268"; a="338925323" X-IronPort-AV: E=Sophos;i="5.90,136,1643702400"; d="scan'208";a="338925323" Received: from orsmga007.jf.intel.com ([10.7.209.58]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 25 Feb 2022 04:49:52 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.90,136,1643702400"; d="scan'208";a="533559561" Received: from silpixa00401183.ir.intel.com ([10.55.129.105]) by orsmga007.jf.intel.com with ESMTP; 25 Feb 2022 04:49:51 -0800 From: Tadhg Kearney To: reshma.pattan@intel.com Cc: dts@dpdk.org, Tadhg Kearney Subject: [dts][PATCH 1/2] test_plans/vm_power_manager_test_plans: remove multivm test Date: Fri, 25 Feb 2022 12:49:28 +0000 Message-Id: <20220225124929.674983-2-tadhg.kearney@intel.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20220225124929.674983-1-tadhg.kearney@intel.com> References: <20220225124929.674983-1-tadhg.kearney@intel.com> MIME-Version: 1.0 X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dts-bounces@dpdk.org Signed-off-by: Tadhg Kearney --- 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 - vmpower> add_channels all - vmpower> show_cpu_freq - -6. Add VM2 in host and check vm_power_mgr can get frequency normally:: - - vmpower> add_vm - vmpower> add_channels all - vmpower> show_cpu_freq - -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