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;
Subject: Re: [PATCH] cpuidle: Add "cpuidle.use_deepest" to bypass governor and
 allow HW to go deep
To:     Len Brown <lenb@kernel.org>
Cc:     dsmythies@telus.net, linux-pm@vger.kernel.org,
        jacob.jun.pan@linux.intel.com, linux-kernel@vger.kernel.org,
        Len Brown <len.brown@intel.com>
References: <1d81edef71c936099f8bb9d16162f8e70fbe401c.1510212816.git.len.brown@intel.com>
From:   Thomas Ilsche <thomas.ilsche@tu-dresden.de>
Message-ID: <9371b55d-c4eb-c3e0-aadf-f624ec72a83f@tu-dresden.de>
Date:   Thu, 16 Nov 2017 17:11:28 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <1d81edef71c936099f8bb9d16162f8e70fbe401c.1510212816.git.len.brown@intel.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On 2017-11-09 08:38, Len Brown wrote:
> From: Len Brown <len.brown@intel.com>
> 
> While there are several mechanisms (cmdline, sysfs, PM_QOS) to limit
> cpuidle to shallow idle states, there is no simple mechanism
> to give the hardware permission to enter the deeptest state permitted by PM_QOS.
> 
> Here we create the "cpuidle.use_deepest" modparam to provide this capability.
> 
> "cpuidle.use_deepest=Y" can be set at boot-time, and
> /sys/module/cpuidle/use_deepest can be modified (with Y/N) at run-time.

This is a good option to have and can conveniently prevent idle power consumption
issues. But that wouldn't be a reasonable default, would it?
I still think there is an inherent need for a heuristic and a corresponding
mitigation to avoid staying in a sleep state too long.

Best,
Thomas


From 1583700433273808768@xxx Fri Nov 10 17:20:28 +0000 2017
X-GM-THRID: 1583573317012724483
X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread