Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp4564345imm; Fri, 18 May 2018 07:11:50 -0700 (PDT) X-Google-Smtp-Source: AB8JxZpZDI91ZwvXI5eTc/x+/fFM44Wz7mUPKXk9bgKx/3xca2hISoxa3TCpGArReqJogyMWPCl8 X-Received: by 2002:a17:902:26a:: with SMTP id 97-v6mr9688006plc.367.1526652710509; Fri, 18 May 2018 07:11:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526652710; cv=none; d=google.com; s=arc-20160816; b=KU8kXtVjGK3jMWxHmjsji/OQGeqzbieOblVC0MWB9y9uskvK7eTg/itElOFW6xKiQq zp8Kv6yssBKw49fxCK0yxKsKHT2D9y/uoAVuj37NS8518NXkbSlG3bFNIvVVbOsZgq3v mbQmB90uP/v3XKSqYYRlvfGamT5tSJU/LTuDJUTiE1mKFIa0A8odUCGhG3ASrOXzyaWO lyAIFVwZOXlqEHcE1QH5R9cYWZMg6l3Q8+CtyGgkRjHxrp74/lf/ZOmpmu59eln39IVc 2EuKHnOeUuUHHoPUdn3fF0001XRzCkwNava73y27x7KG33z633g3Yzc7axWrB/gPXaCx Ai6Q== 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=e37gfhi45ZO0JkwU1xXTcdO1MOQLroTc7cJyfytuVWw=; b=vnIkk/oZsW7PP2yKq1Q6TZ7N7LhSREM0eD6gJKKkLtvBTX0Ty5UdRW9lDL8gCGAQcA FWeHIqiC5tQ4IAGcVfbOMjhP2qeO6c1iSP1SaMatc+ec/+mN5n+vROWaMBW1ELHoEPTx /8Yoa61wA5WR0ulpAGXgt2zQ4HhZGJXp8IFJWbuxwlwIufKfMj383l6Pv/8UGuFyzPsB Oyk5iwt6gvdAWWfmrn5FkhW84UwT/kSBZnWSigFCYQ0ObY3vnyT2kLEWe4w17oP2kA4f ErnOZwfIixK+xquYmZ2f3EQ5YkEMQYpCPHxMvd/8DV3ybAtGcmX/CBKvZmRlcswXyP9b EhRA== 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 o2-v6si5802802pgv.486.2018.05.18.07.11.12; Fri, 18 May 2018 07:11:50 -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 S1752748AbeEROJ3 (ORCPT + 99 others); Fri, 18 May 2018 10:09:29 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:53570 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752451AbeEROJZ (ORCPT ); Fri, 18 May 2018 10:09:25 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id F212A1435; Fri, 18 May 2018 07:09:24 -0700 (PDT) Received: from [10.1.206.36] (e113632-lin.cambridge.arm.com [10.1.206.36]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPA id 8FE8F3F24A; Fri, 18 May 2018 07:09:22 -0700 (PDT) Subject: Re: [RFC/RFT] [PATCH 02/10] cpufreq: intel_pstate: Conditional frequency invariant accounting To: Peter Zijlstra , Patrick Bellasi Cc: "Rafael J. Wysocki" , Srinivas Pandruvada , Juri Lelli , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Len Brown , "Rafael J. Wysocki" , Mel Gorman , the arch/x86 maintainers , Linux PM , Viresh Kumar , Linux Kernel Mailing List References: <20180516154733.GF12198@hirez.programming.kicks-ass.net> <20180516163105.GP28366@localhost.localdomain> <20180517105907.GC22493@localhost.localdomain> <20180517150418.GF22493@localhost.localdomain> <1526571692.11765.10.camel@linux.intel.com> <20180517161649.GX12217@hirez.programming.kicks-ass.net> <1526575358.11765.14.camel@linux.intel.com> <20180517182803.GY12217@hirez.programming.kicks-ass.net> <20180518105742.GN30654@e110439-lin> <20180518112919.GI12217@hirez.programming.kicks-ass.net> From: Valentin Schneider Message-ID: Date: Fri, 18 May 2018 15:09:21 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180518112919.GI12217@hirez.programming.kicks-ass.net> 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 Hi, On 18/05/18 12:29, Peter Zijlstra wrote: > On Fri, May 18, 2018 at 11:57:42AM +0100, Patrick Bellasi wrote: >> Thus, my simple (maybe dumb) questions are: >> - why can't we just fold turbo boost frequency into the existing concepts? >> - what are the limitations of such a "simple" approach? > > Perhaps... but does this not further complicate the whole capacity vs > util thing we already have in say the misfit patches? What do you mean by that ? Bear in mind, I'm a complete stranger to turbo boost so I fail to see why, as Patrick puts it, it can't fit within the existing concepts (i.e. max util is 1024 but is only reachable when turbo boosted).