On 30/09/2019 14:00, David Hunt wrote:
From: Marcin Hajkowski <marcinx.hajkow...@intel.com> Send request to power manager for core id provided by user to get related capabilities. Signed-off-by: Marcin Hajkowski <marcinx.hajkow...@intel.com> Tested-by: David Hunt <david.h...@intel.com> Acked-by: Lee Daly <lee.d...@intel.com> --- .../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 <david.h...@intel.com>
