Received: by 2002:ac0:950c:0:0:0:0:0 with SMTP id f12csp4203663imc; Thu, 14 Mar 2019 15:09:06 -0700 (PDT) X-Google-Smtp-Source: APXvYqyduH9MG6CkvwE/ebHvX2fVPTju8Hvf2ehGK0RAHrV3iO2FslVUgH6EZjkWHoAlkxh51+tc X-Received: by 2002:a63:1602:: with SMTP id w2mr124122pgl.406.1552601345990; Thu, 14 Mar 2019 15:09:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1552601345; cv=none; d=google.com; s=arc-20160816; b=LzHtexGBFMn/1qkXPU3rEBHfuK3oE/hbSo/hB6VcgGQSGIeqPmb1jvZtaqAxv7GIbr 7OhZp4DA2zz/PRUGQKGRk2a9606CMa0lXNxdQkZhM4cZyzOkJIUQzlernD2OyPx0N8td j6CosZ37dFBKRH6wLqrdaoSa5/RJA5MEx2/df/FFW6qq6sOi5USIjANkWpXz+UVP725L JtAMbITJn4bt20JZ2zywtR1MyyjZ6/5TuNnNvLpOHFAZ+YFCJcDbneaXLAZmww+0DTLu mLF7SzU9OHLrchxnV5i/IVlAYnBOvSvINbGHU+x7ZZarNhpcWlmWF8P5Og3Cb3auOI5O Rhiw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version; bh=GXCPmTlnAZhHllNvpnoywKNTmWdgGF6QJBXrvsJXaE8=; b=kJOJyDUPXga/WUF7TmxwhWV0627NCckfnVnDKVeeSdmxji2FpZXUsybMXEZfufcqZC qCVowGuAIbfQY0g5/W1/hqxZIqUWw9TXsPBtOBjl2040QYtDn/Q1lEazsvb3yE81lebp bqKjka2VderTpVS6jp10pVAcYO+WLERg6sQ+8h4Q8+kU+Pe+BxtPzgNciPprWxOy2P4Q cmEHbAL+UWxlPl8KNO1z4FgG3fPdujyP1lspgFbdbfPgwKbn3ucHWzJhMvWb6zQklavM XP9bj1BVaz05P1e1wLdLH2Hb1LiwlWUJItHSgiWdTJBsE2/SZUn7+CzlllDjnHZDM2YZ v1GA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p7si133699pgk.411.2019.03.14.15.08.50; Thu, 14 Mar 2019 15:09:05 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727458AbfCNWIQ (ORCPT + 99 others); Thu, 14 Mar 2019 18:08:16 -0400 Received: from mail-ot1-f68.google.com ([209.85.210.68]:39382 "EHLO mail-ot1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726885AbfCNWIP (ORCPT ); Thu, 14 Mar 2019 18:08:15 -0400 Received: by mail-ot1-f68.google.com with SMTP id e15so6612529otk.6; Thu, 14 Mar 2019 15:08:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=GXCPmTlnAZhHllNvpnoywKNTmWdgGF6QJBXrvsJXaE8=; b=h1ikMsNYTsDEoicI+4CKjJplgfrTZUm+y7ZneuLBrjFMf3KlecIgL18/72vYBWD9n5 Qib5mPNI1xYbkx4DPLbvgJkWScl2eQ9tNiLZxBqI/UqWZofJYnUXYfE2gAk5in2OEVLN Vpzy6s7TNa3gfVSYa7AXnGuMKV2djwpL2wFdwHKNHygWQU/NKEFSkoZjUZ4raILPDrsV +Ix8+1y1XaKNUMC5wyfCmmPd+Puu607tmnwD/+F9Cyg2m3uLzqoHF6avYLyBg810uB3G ityCgJuKXuTIC8hHxUKG7sb5b+BBOugMc/9QANHudx3BFQPexF9EzuT20LmCy+GPkhz4 BFTQ== X-Gm-Message-State: APjAAAVD+75rl/0Z4pTdl1WBPCOmDEwaaGXdAJnigjepNRCEJfUZ6cA+ m5qZOg9diI0zoeY6FowO1afrFx450cp77uDI/NI= X-Received: by 2002:a9d:4e08:: with SMTP id p8mr193749otf.124.1552601294428; Thu, 14 Mar 2019 15:08:14 -0700 (PDT) MIME-Version: 1.0 References: <6369897.qxlu8PgE1t@house> In-Reply-To: <6369897.qxlu8PgE1t@house> From: "Rafael J. Wysocki" Date: Thu, 14 Mar 2019 23:08:03 +0100 Message-ID: Subject: Re: [PATCH] [RESEND] Do not modify perf bias performance setting by default at boot To: Thomas Renninger Cc: Len Brown , Rafael Wysocki , Hannes Reinecke , Linux PM , LKML , Borislav Petkov , Simon Schricker , Srinivas Pandruvada , Len Brown Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Mar 14, 2019 at 3:42 PM Thomas Renninger wrote: > > This is a revert of mainline git commits: > commit b51ef52df71cb28e9d90cd1d48b79bf19f0bab06 > commit 17edf2d79f1ea6dfdb4c444801d928953b9f98d6 > commit abe48b108247e9b90b4c6739662a2e5c765ed114 I'm not quite convinced that reverting these is the right thing to do here. > It is about this kernel message showing up on quite a lot servers: > [ 0.072652] ENERGY_PERF_BIAS: Set to 'normal', was 'performance' > [ 0.076003] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8) What happens on boot is a matter of convention and the convention by which the EPB is set to "neutral" at that point has been used for quite a while. Changing it now may confuse some users or even worse. It would be fine to change the log level of these messages in my view, though. > The background afaik were some BIOS which "forgot to set a default value". > Certainly some (one?) broken laptop BIOS was meant, because > the value zero (performance) is quite a reasonable default value on server systems > and this is how a lot CPUs typically come up there. That depends on the expected power/perf profile of the system and the kernel has no information regarding that. Arguably, user space can set the EPB to whatever it wants at the init time according to the information it has. It is not quite realistic to expect that either the BIOS or the kernel will do the right thing on all systems in that respect anyway. > Another sever bug with above patches: > If you really set performance BIAS MSR value to 'performance' > as mentioned in kernel boot log, it is reset on next CPU offline/online cycle > (see below). That is a bug. There is no reason to change the EPB on CPU offline/online and I agree that this needs to be fixed. The reverts would make this problem go away, but that's not the only possible way to fix it. Moreover, what is done during system-wide resume appears to be a bug too. Whatever EPB value is there during suspend should be saved and it should be restored during resume. Reverting the commits above will not fix that particular issue. Thanks, Rafael