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 8BD77A04A4; Tue, 26 May 2020 11:24:20 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 102511DA43; Tue, 26 May 2020 11:24:20 +0200 (CEST) Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 46D001DA41 for ; Tue, 26 May 2020 11:24:18 +0200 (CEST) IronPort-SDR: EvGcOH7hDwKkAlvK5DJEHl2Gb9I9fmG+G3fYvdURwRvNdMOYNi4i1z/7MOjfs5TLDDJ1Ki8bLj D0bwHg0YBfjA== X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 26 May 2020 02:24:17 -0700 IronPort-SDR: Ay+RJrvPY0fLIsr1nPjVLHWXlmV1CvSBe/gqhPeK+SHSqVVvmEjqZ5RO6SlYXHKettISq6v0aR 47qj5QddhThw== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.73,436,1583222400"; d="scan'208";a="375644427" Received: from krnacejr-mobl.amr.corp.intel.com (HELO [10.209.43.93]) ([10.209.43.93]) by fmsmga001.fm.intel.com with ESMTP; 26 May 2020 02:24:15 -0700 To: oulijun , "Hunt, David" , David Marchand Cc: Van Haaren Harry , dev , "Pattan, Reshma" References: <3aeeb17b-66d0-cf87-df3a-0e2c313ba9ee@intel.com> From: "Burakov, Anatoly" Message-ID: <918a8ac5-cf98-e200-605d-a87dd78a1630@intel.com> Date: Tue, 26 May 2020 10:24:15 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] =?utf-8?b?44CQQlVHIFJFUE9SVOOAkWwzZndkLXBvd2VyIGNhbiBu?= =?utf-8?q?ot_exit_by_ctrl+c?= 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 26-May-20 4:50 AM, oulijun wrote: > Hi， >    I have update the code into 20.05-rc2. However， the l3fwd-power > startup fail. > > [root@centos-C3 build]# l3fwd-power -w 0000:7d:00.1  -c 0xc000000 -n 4 > -- -P -p 0x01 --config '(0,0,27)' --parse-ptype > EAL: Detected 128 lcore(s) > EAL: Detected 4 NUMA nodes > EAL: Multi-process socket /var/run/dpdk/rte/mp_socket > EAL: Selected IOVA mode 'PA' > EAL: No available hugepages reported in hugepages-2048kB > EAL: No available hugepages reported in hugepages-32768kB > EAL: No available hugepages reported in hugepages-64kB > EAL: Probing VFIO support... > EAL: VFIO support initialized > EAL:   using IOMMU type 1 (Type 1) > EAL: Ignore mapping IO port bar(1) > EAL: Ignore mapping IO port bar(3) > EAL: Probe PCI driver: net_hns3 (19e5:a221) device: 0000:7d:00.1 (socket 0) > No telemetry legacy support - No legacy callbacks, legacy socket not > created > Promiscuous mode selected > soft parse-ptype is enabled > POWER: Env isn't set yet! > POWER: Attempting to initialise ACPI cpufreq power management... > POWER: Power management governor of lcore 26 has been set to user space > successfully > POWER: File not opened > POWER: Cannot get available frequencies of lcore 26 > POWER: Attempting to initialise PSTAT power management... > POWER: Power management governor of lcore 26 has been set to performance > successfully > POWER: Error opening '/dev/cpu/26/msr': No such file or directory > POWER: Cannot init for setting frequency for lcore 26 > POWER: Attempting to initialise VM power management... > GUEST_CHANNEL: Opening channel > '/dev/virtio-ports/virtio.serial.port.poweragent.26' for lcore 26 > GUEST_CHANNEL: Unable to to connect to > '/dev/virtio-ports/virtio.serial.port.poweragent.26' with error No such > file or directory > POWER: Unable to set Power Management Environment for lcore 26 > POWER: Library initialization failed on core 26 > EAL: Error - exiting with code: 1 >   Cause: init_power_library failed > > Thanks > Lijun Ou > Hi, Previously, l3fwd-power was very lax in what it was allowing. Now, if it can't enable power management, it will not run, because it is more strict in what it allows. As is shown in the log, it tries to initialize ACPI power management, but fails. Then, it tries to initialize pstate mode, and it appears that MSR driver is not loaded, so it doesn't work either. It also tries to check if a KVM channel exists, which doesn't, and that fails as well. So, no power management environment can be enabled, and the application fails to start. In order to make it work, you should either boot in ACPI mode (kernel parameter: "intel_pstate=disable"), or load the MSR driver (root command: modprobe msr). This more strict power library initialization was added because we saw people misusing l3fwd-power to attempt to run without power management environment being initialized (such as inside a VM while not having telemetry mode enabled), which it was not designed to do and which would be an invalid test. -- Thanks, Anatoly