Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932402AbcCHMOc (ORCPT ); Tue, 8 Mar 2016 07:14:32 -0500 Received: from mx2.suse.de ([195.135.220.15]:34577 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932068AbcCHMOY (ORCPT ); Tue, 8 Mar 2016 07:14:24 -0500 From: Thomas Renninger To: Len Brown , Ingo Molnar Cc: "Rafael J. Wysocki" , X86 ML , Linux Kernel Mailing List , "linux-pm@vger.kernel.org" Subject: Re: [PATCH] Do not modify MSR_IA32_ENERGY_PERF_BIAS in kernel Date: Tue, 08 Mar 2016 13:14:16 +0100 Message-ID: <1500934.JjcSpplzao@skinner> User-Agent: KMail/4.14.9 (Linux/3.16.7-29-desktop; KDE/4.14.9; x86_64; ; ) In-Reply-To: References: <4687430.mfM0GbdeDL@skinner> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1617 Lines: 40 On Monday, March 07, 2016 07:50:57 PM Len Brown wrote: > > But with Broadwell-EP processor (E5-2687W v4) the CPU will not enter turbo > > modes if this value is not set to performance > > BDX-EP supports HWP. > Are these failing machines running in HWP mode? > > (On BDX-EP, and only on BDX-EP, EPB acts to set the BIAS for HWP, > because that processor doesn't yet have EPP.) I am not sure whether I can publish platform info. I asked for and added you to CC of the private bug a while ago. This kernel is run: SLES12 SP1, 3.12.49-4-default I grepped the whole supportconfig for -i hwp and couldn't find anything, so I very much expect this machine is/was not run in HWP mode, right? I still question the usefulness of the "initialize perf bias to normal" hack. For our distro I am pretty sure, we do not want to have this one and we prefer the CPU or BIOS initialized value, even (or especially) if it is set to performance. Are there any known platforms where this would really be an issue and how sever would it be? I already removed the "set perf bias to normal" years ago for SLE11 without getting any regression or negative reports. Now finding the workaround on the hack to run a suspend hook to adjust perf bias value on each suspend cycle... This is going into a wrong direction. I agree that if this needs resetting after each suspend cycle, userspace should not need to care about it. I could imagine a sysfs variable here: /sys/devices/system/cpu/intel_pstate/perf_bias but the static setting from 0 to 6 in the x86 core code and the suspend callback should get reverted, right? Thomas