From patchwork Thu Sep 24 09:45:39 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: "Hunt, David" X-Patchwork-Id: 78665 Return-Path: X-Original-To: patchwork@inbox.dpdk.org Delivered-To: patchwork@inbox.dpdk.org Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 37EAEA04B1; Thu, 24 Sep 2020 11:45:49 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 282AD1DD94; Thu, 24 Sep 2020 11:45:48 +0200 (CEST) Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 523231DD86 for ; Thu, 24 Sep 2020 11:45:46 +0200 (CEST) IronPort-SDR: eMShcg1tl4+dqRgTRKPzR1JUtUzOSHrxuruYYmnHKE+iT84JVeGlXzZTGpuJj+pHbA0vmQJCkq 1Xau91LV+yWg== X-IronPort-AV: E=McAfee;i="6000,8403,9753"; a="158527682" X-IronPort-AV: E=Sophos;i="5.77,297,1596524400"; d="scan'208";a="158527682" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 24 Sep 2020 02:45:45 -0700 IronPort-SDR: 5d27phf7Dp4sH1L8AXvr0GwWlx9QpisgVufLdNdD33Dgh1FhK/K6iwhMXGEqV/u0aZnGiUmvHI Yl3Lto98HLng== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.77,297,1596524400"; d="scan'208";a="291119419" Received: from silpixa00399952.ir.intel.com (HELO silpixa00399952.ger.corp.intel.com) ([10.237.222.38]) by fmsmga007.fm.intel.com with ESMTP; 24 Sep 2020 02:45:44 -0700 From: David Hunt To: dev@dpdk.org Cc: David Hunt Date: Thu, 24 Sep 2020 10:45:39 +0100 Message-Id: <20200924094539.17998-1-david.hunt@intel.com> X-Mailer: git-send-email 2.17.1 Subject: [dpdk-dev] [PATCH v2] doc: remove make info from vm power apps X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Now that make is deprecated, remove any reference from the build instructions for vm_power_manager and guest_cli Signed-off-by: David Hunt --- .../sample_app_ug/vm_power_management.rst | 66 +++---------------- 1 file changed, 9 insertions(+), 57 deletions(-) diff --git a/doc/guides/sample_app_ug/vm_power_management.rst b/doc/guides/sample_app_ug/vm_power_management.rst index 1b6de8e93..a486d2af2 100644 --- a/doc/guides/sample_app_ug/vm_power_management.rst +++ b/doc/guides/sample_app_ug/vm_power_management.rst @@ -241,18 +241,7 @@ see :doc:`compiling`. The application is located in the ``vm_power_manager`` subdirectory. -To build just the ``vm_power_manager`` application using ``make``: - -.. code-block:: console - - export RTE_SDK=/path/to/rte_sdk - export RTE_TARGET=build - cd ${RTE_SDK}/examples/vm_power_manager/ - make - -The resulting binary is ``${RTE_SDK}/build/examples/vm_power_manager``. - -To build just the ``vm_power_manager`` application using ``meson``/``ninja``: +To build the ``vm_power_manager`` application: .. code-block:: console @@ -274,7 +263,7 @@ than the EAL options: .. code-block:: console - ./build/vm_power_mgr [EAL options] + ./examples/dpdk-vm_power_mgr [EAL options] The application requires exactly two cores to run. One core for the CLI and the other for the channel endpoint monitor. For example, to run on @@ -282,7 +271,7 @@ cores 0 and 1 on a system with four memory channels, issue the command: .. code-block:: console - ./build/vm_power_mgr -l 0-1 -n 4 + ./examples/dpdk-vm_power_mgr -l 0-1 -n 4 After successful initialization, the VM Power Manager CLI prompt appears: @@ -457,44 +446,7 @@ For compiling and running the ``l3fwd-power`` sample application, see The application is in the ``guest_cli`` subdirectory under ``vm_power_manager``. -To build just the ``guest_vm_power_manager`` application using ``make``, issue -the following commands: - -.. code-block:: console - - export RTE_SDK=/path/to/rte_sdk - export RTE_TARGET=build - cd ${RTE_SDK}/examples/vm_power_manager/guest_cli/ - make - -The resulting binary is ``${RTE_SDK}/build/examples/guest_cli``. - -**Note**: This sample application conditionally links in the Jansson JSON -library. Consequently, if you are using a multilib or cross-compile -environment, you may need to set the ``PKG_CONFIG_LIBDIR`` environmental -variable to point to the relevant ``pkgconfig`` folder so that the correct -library is linked in. - -For example, if you are building for a 32-bit target, you could find the -correct directory using the following find command: - -.. code-block:: console - - # find /usr -type d -name pkgconfig - /usr/lib/i386-linux-gnu/pkgconfig - /usr/lib/x86_64-linux-gnu/pkgconfig - -Then use: - -.. code-block:: console - - export PKG_CONFIG_LIBDIR=/usr/lib/i386-linux-gnu/pkgconfig - -You then use the ``make`` command as normal, which should find the 32-bit -version of the library, if it installed. If not, the application builds -without the JSON interface functionality. - -To build just the ``vm_power_manager`` application using ``meson``/``ninja``: +To build the ``dpdk-guest_cli`` application: .. code-block:: console @@ -506,7 +458,7 @@ To build just the ``vm_power_manager`` application using ``meson``/``ninja``: meson configure -Dexamples=vm_power_manager/guest_cli ninja -The resulting binary is ``${RTE_SDK}/build/examples/guest_cli``. +The resulting binary is ``${RTE_SDK}/build/examples/dpdk-guest_cli``. Running the Guest Application ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -515,14 +467,14 @@ The standard EAL command line parameters are necessary: .. code-block:: console - ./build/vm_power_mgr [EAL options] -- [guest options] + ./examples/dpdk-guest_cli [EAL options] -- [guest options] The guest example uses a channel for each lcore enabled. For example, to run on cores 0, 1, 2 and 3: .. code-block:: console - ./build/guest_vm_power_mgr -l 0-3 + ./examples/dpdk-guest_cli -l 0-3 .. _sending_policy: @@ -593,7 +545,7 @@ host, use a command like the following: .. code-block:: console - ./build/guest_vm_power_mgr -l 0-3 -n 4 -- --vm-name=ubuntu --policy=BRANCH_RATIO --vcpu-list=2-4 + ./examples/dpdk-guest_cli -l 0-3 -n 4 -- --vm-name=ubuntu --policy=BRANCH_RATIO --vcpu-list=2-4 Once the VM Power Manager Guest CLI appears, issuing the 'send_policy now' command will send the policy to the host: @@ -707,7 +659,7 @@ To start the application and configure the power policy, and send it to the host .. code-block:: console - ./build/guest_vm_power_mgr -l 0-3 -n 4 -- --vm-name=ubuntu --policy=BRANCH_RATIO --vcpu-list=2-4 + ./examples/dpdk-guest_cli -l 0-3 -n 4 -- --vm-name=ubuntu --policy=BRANCH_RATIO --vcpu-list=2-4 Once the VM Power Manager Guest CLI appears, issuing the 'send_policy now' command will send the policy to the host: