From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id E479BA2EDB for ; Mon, 30 Sep 2019 15:04:22 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id B0C453237; Mon, 30 Sep 2019 15:04:21 +0200 (CEST) Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by dpdk.org (Postfix) with ESMTP id F0EFC2A6C for ; Mon, 30 Sep 2019 15:04:19 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Sep 2019 06:04:19 -0700 X-IronPort-AV: E=Sophos;i="5.64,567,1559545200"; d="scan'208";a="390816222" Received: from dhunt5-mobl4.ger.corp.intel.com (HELO [10.237.221.113]) ([10.237.221.113]) by fmsmga005-auth.fm.intel.com with ESMTP/TLS/AES256-SHA; 30 Sep 2019 06:04:18 -0700 Cc: dev@dpdk.org, Marcin Hajkowski References: <20190530161517.11916-2-marcinx.hajkowski@intel.com> <20190930130043.2885-1-david.hunt@intel.com> <20190930130043.2885-4-david.hunt@intel.com> From: "Hunt, David" Message-ID: Date: Mon, 30 Sep 2019 14:04:16 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2 MIME-Version: 1.0 In-Reply-To: <20190930130043.2885-4-david.hunt@intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Subject: Re: [dpdk-dev] [PATCH v2 3/3] examples/power_guest: send request for specified core capabilities 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" On 30/09/2019 14:00, David Hunt wrote: > From: Marcin Hajkowski > > Send request to power manager for core id provided > by user to get related capabilities. > > Signed-off-by: Marcin Hajkowski > Tested-by: David Hunt > Acked-by: Lee Daly > --- > .../guest_cli/vm_power_cli_guest.c | 119 +++++++++++++++++- > 1 file changed, 117 insertions(+), 2 deletions(-) > --snip-- Some of the steps to test included blow: In the Host, enable queries via the virtio-serial interface from the guest to the host: vmpower> set_query ubuntu3 enable In an SST-BF enabled host, with 6 high priority cores per socket, query the list of high prioroty cores with the sst_bf.py python script (https://github.com/intel/commspowermanagement): root@silpixa00399952:~# sst_bf.py -l 1,6,7,8,9,16,21,26,27,28,29,30 0x7c2103c2 In the host, query the cores used by the VM: vmpower> show_vm ubuntu3 ...snip... Virtual CPU(s): 8   [0]: Physical CPU 28   [1]: Physical CPU 29   [2]: Physical CPU 30   [3]: Physical CPU 31   [4]: Physical CPU 32   [5]: Physical CPU 33   [6]: Physical CPU 34   [7]: Physical CPU 35 So we now know that cores 28,29 and 30 should show up as high priority in the VM. So, from the VM side, we use the new 'query_cpu_caps' command to see the capabilities of each core: vmpower(guest)> query_cpu_caps all Capabilities of [0] vcore are: turbo possibility: 1, is priority core: 1. Capabilities of [1] vcore are: turbo possibility: 1, is priority core: 1. Capabilities of [2] vcore are: turbo possibility: 1, is priority core: 1. Capabilities of [3] vcore are: turbo possibility: 1, is priority core: 0. Capabilities of [4] vcore are: turbo possibility: 1, is priority core: 0. Capabilities of [5] vcore are: turbo possibility: 1, is priority core: 0. Capabilities of [6] vcore are: turbo possibility: 1, is priority core: 0. Capabilities of [7] vcore are: turbo possibility: 1, is priority core: 0. As expected, vcore 0,1,2 (pcore 28,29,30) are high priority cores. Tested-by: David Hunt