From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932249AbdJQHcu (ORCPT ); Tue, 17 Oct 2017 03:32:50 -0400 Received: from mga02.intel.com ([134.134.136.20]:35320 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753611AbdJQHct (ORCPT ); Tue, 17 Oct 2017 03:32:49 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.43,389,1503385200"; d="scan'208";a="163473298" Subject: Re: [RFC PATCH v2 0/8] Introduct cpu idle prediction functionality To: "Rafael J. Wysocki" Cc: Aubrey Li , tglx@linutronix.de, peterz@infradead.org, len.brown@intel.com, ak@linux.intel.com, tim.c.chen@linux.intel.com, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org References: <1506756034-6340-1-git-send-email-aubrey.li@intel.com> <3026355.QRuoy6eIZM@aspire.rjw.lan> <3251888.IpbWLYog7H@aspire.rjw.lan> From: "Li, Aubrey" Message-ID: Date: Tue, 17 Oct 2017 15:32:45 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <3251888.IpbWLYog7H@aspire.rjw.lan> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2017/10/17 8:07, Rafael J. Wysocki wrote: > On Monday, October 16, 2017 9:44:41 AM CEST Li, Aubrey wrote: >> >> Or you concern why the threshold can't simply be tick interval? > > That I guess. > >> For the latter, if the threshold is close/equal to the tick, it's quite possible >> the next event is the tick and no other else event. > > Well, I don't quite get that. > > What's the reasoning here? if we set the threshold to the tick interval, when the system keeps the tick on once, it will have no chance to turn if off forever. Because we turn on the tick, and count in the time of idle entry and idle exit, the idle interval always < tick interval, that means idle is always a short idle. Thanks, -Aubrey