From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] examples/power: fix intel pstate power manager Date: Tue, 15 Jan 2019 00:07:17 +0100 Message-ID: <13123252.86QpxeBMBg@xps> References: <20190108152523.39944-1-david.hunt@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, liang.j.ma@intel.com To: David Hunt Return-path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 955868E76 for ; Tue, 15 Jan 2019 00:07:20 +0100 (CET) In-Reply-To: <20190108152523.39944-1-david.hunt@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 08/01/2019 16:25, David Hunt: > The vm_power_manager starts by setting the environment to acpi > using rte_power_set_env(PM_ENV_ACPI_CPUFREQ). This causes a problem > starting vm_power_manager when the system is using the intel_pstate > driver. The env should be set to none, or not called at all, because > the library now auto-detects the environment to be either acpi or > intel_pstate. This patch sets the environment to none so that the > library can successfully auto-detect. > > Fixes: e6c6dc0f96c8 ("power: add p-state driver compatibility") > > Signed-off-by: David Hunt Applied, thanks