From mboxrd@z Thu Jan 1 00:00:00 1970 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) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 306B328BEE; Mon, 14 Jan 2019 18:07:20 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Mon, 14 Jan 2019 18:07:20 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=uh40qCGhM7zjix2luScJ+Q0LiWQgGrgFcI/iD70NM7A=; b=Gj1/601+wWzL 4PHdT7Hzc19clMQzH2f4C1lF5BzSvyGF2Cn/Gs/F1cgI5mqgfvhjmowINbzTEvcO +/1eaDkamP2P3D8AmYdySJF2mEDhe67skC7cCs2rNa7J2WzhYyUnXBRL7hV/CAUk eMYwArYyf8vfD/ib/MqR7+7aEtnRqX4= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=uh40qCGhM7zjix2luScJ+Q0LiWQgGrgFcI/iD70NM 7A=; b=efH4oUo1SdD1FAHM035SAZeiwf0uqPNm5P+QmW2XBlshBAqFDHfORyAOO v5uOMpQsYF8cJGXrCbCqrbGeO3o6ctDYLqhiZQ5Mi+mnDhW1NhBjJevjxQ+/8/L9 wcffPJp2B1Ld2UsWCEm2M1BNAWJfdjwSyvrH9eWJ1n2jemv/zWnozoQnK/oLuJ9W DswvbvJQdjr+1sB/IFmjQMH61naGyEpuuq0IBuv79MFIfVQFDOSUKrpyKn5ezvkB KwSwH+W6zOyz1tXgSFocWXKBhZ5b878nRW7vgpn0lh3uLw3+GQIYCP7bbUNM4E6j 6xApbi8Z6VieEeoTD9oqZCex+cE/w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrgedvgddtgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt tdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhephffvufffkfgjfh gggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceo thhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukfhppeejjedrudefgedrvddtfe drudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhho nhdrnhgvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id C29CB102A0; Mon, 14 Jan 2019 18:07:18 -0500 (EST) From: Thomas Monjalon To: David Hunt Cc: dev@dpdk.org, liang.j.ma@intel.com Date: Tue, 15 Jan 2019 00:07:17 +0100 Message-ID: <13123252.86QpxeBMBg@xps> In-Reply-To: <20190108152523.39944-1-david.hunt@intel.com> References: <20190108152523.39944-1-david.hunt@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] examples/power: fix intel pstate power manager 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: , X-List-Received-Date: Mon, 14 Jan 2019 23:07:20 -0000 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