Received: by 10.223.164.221 with SMTP id h29csp1716351wrb; Tue, 17 Oct 2017 08:04:38 -0700 (PDT) X-Google-Smtp-Source: AOwi7QDbH0v+SH4EwBeSZfXTwNdR98w41EDzltwJcpLzv87UYRHN19+iFytVUt1S1jpVLp9ML1Ap X-Received: by 10.84.178.164 with SMTP id z33mr12151751plb.333.1508252678178; Tue, 17 Oct 2017 08:04:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1508252678; cv=none; d=google.com; s=arc-20160816; b=KDzUAoxWqzTvmr5VsbvVkBSKavXTObVNF9Q4+jR504qcArn4IwnK4loxZYUdSBAopw vm+4wiftqcruO4a26T3s0rW2RK8gCQ2Dk5HRSgg30PAIPZSD5YEtRX3f/tufMcugxMpE jcP/NMnK9Lbi9fvRbdQY8pDW0q7CWFOJV8yedrWWWPG03MIlUvPwhcE56tFUKRpKOQpl KGdyASwPcZE4/1OsWDuw14UpPzUo1Y42OTrKnzUvRX4q7GKRhSmyoTBzGzcuItQO99lC K36P1gwF3nHoGSPpBdQFOMC/jf3KLddaNIhRdhKTnqYZAQXcnVIsEzuIYWKePqWBLjDG FRSA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=Z9g+zMAHW+9FmMqvhSxexryXbTO4wjy/OSJd3f0Sics=; b=rXK/XnacPME1olW7ko0oDUw2aNTb8LkU+cjAW9MA4EHKll9l3TEBozqewQc7+W2U/0 9w6EX2RXNWSy32+xCfNOx0NQMgUGEH70EY7OjVUNmkGEu5lXOfhQNLBQ6yVI/UTxpN7K Uz4pkrHcd/HtlvSzB7LvFp7c2CveG3f+A6mTSd0ds9GChKYII9Spd+PsQJmrxNB9oNwH VdApDIO0pqLzmnsQKntsxUgyJwdIo9Z68DnIg6u5Il8U7Ib7VBnWFvfU/532V9+nFc/h wvNJ9aDeIpcki4G09abzAb9yuDopWAumuOSbdnsEAKiTrb7kTO03D4qz/RzDVMmKMEsh +gEw== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h13si1343188pfi.64.2017.10.17.08.04.22; Tue, 17 Oct 2017 08:04:38 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932223AbdJQHcu (ORCPT + 99 others); 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 Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Oct 2017 00:32:48 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.43,389,1503385200"; d="scan'208";a="163473298" Received: from cli6-desk1.ccr.corp.intel.com (HELO [10.239.13.116]) ([10.239.13.116]) by fmsmga005.fm.intel.com with ESMTP; 17 Oct 2017 00:32:46 -0700 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 Precedence: bulk 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 From 1581491497919299336@xxx Tue Oct 17 08:10:23 +0000 2017 X-GM-THRID: 1579948553110255952 X-Gmail-Labels: Inbox,Category Forums