From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1756551AbdGXWVO (ORCPT <rfc822;w@1wt.eu>);
        Mon, 24 Jul 2017 18:21:14 -0400
Received: from cloudserver094114.home.net.pl ([79.96.170.134]:52796 "EHLO
        cloudserver094114.home.net.pl" rhost-flags-OK-OK-OK-OK)
        by vger.kernel.org with ESMTP id S1753250AbdGXWUi (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 24 Jul 2017 18:20:38 -0400
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux PM <linux-pm@vger.kernel.org>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
        LKML <linux-kernel@vger.kernel.org>,
        Doug Smythies <dsmythies@telus.net>
Subject: [PATCH 0/2] cpufreq: intel_pstate: Eliminate the PID controller
Date: Tue, 25 Jul 2017 00:10:04 +0200
Message-ID: <6183701.sLtcQDF8CA@aspire.rjw.lan>
User-Agent: KMail/4.14.10 (Linux/4.12.0-rc1+; KDE/4.14.9; x86_64; ; )
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi,

According to testing so far, the P-state selection based on the PID controller
in intel_pstate can be replaced with the P-state selection based on CPU load
with no considerable regressions *and* the PID-based P-state selection is
generally flaky and hard to manage, make intel_pstate use the P-state selection
based on CPU load for all categories of systems and eliminate the PID controller
along with all things related to it from the driver.

[1/2] is the actual elimination.
[2/2] is a simplification possible after [1/2].

Thanks,
Rafael