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 9BBDBA04A4; Wed, 27 May 2020 08:04:13 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 21D7D1D44C; Wed, 27 May 2020 08:04:13 +0200 (CEST) Received: from huawei.com (szxga06-in.huawei.com [45.249.212.32]) by dpdk.org (Postfix) with ESMTP id 96B511D446 for ; Wed, 27 May 2020 08:04:11 +0200 (CEST) Received: from DGGEMS406-HUB.china.huawei.com (unknown [172.30.72.60]) by Forcepoint Email with ESMTP id 02AB2158CB38A396B1D8; Wed, 27 May 2020 14:04:09 +0800 (CST) Received: from [127.0.0.1] (10.67.103.119) by DGGEMS406-HUB.china.huawei.com (10.3.19.206) with Microsoft SMTP Server id 14.3.487.0; Wed, 27 May 2020 14:04:04 +0800 To: "Burakov, Anatoly" , "Hunt, David" , David Marchand CC: Van Haaren Harry , dev , "Pattan, Reshma" References: <3aeeb17b-66d0-cf87-df3a-0e2c313ba9ee@intel.com> <918a8ac5-cf98-e200-605d-a87dd78a1630@intel.com> From: oulijun Message-ID: Date: Wed, 27 May 2020 14:04:04 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: <918a8ac5-cf98-e200-605d-a87dd78a1630@intel.com> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [10.67.103.119] X-CFilter-Loop: Reflected 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" 在 2020/5/26 17:24, Burakov, Anatoly 写道: > 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. I will try it