From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B450CC433FE for ; Wed, 16 Nov 2022 12:20:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233510AbiKPMUt (ORCPT ); Wed, 16 Nov 2022 07:20:49 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35286 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238704AbiKPMTy (ORCPT ); Wed, 16 Nov 2022 07:19:54 -0500 Received: from mail-qk1-f175.google.com (mail-qk1-f175.google.com [209.85.222.175]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BB460DFA6; Wed, 16 Nov 2022 04:17:59 -0800 (PST) Received: by mail-qk1-f175.google.com with SMTP id v8so11422783qkg.12; Wed, 16 Nov 2022 04:17:59 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=vIWijkKIIG3mmZeimTFZ3ib2SY8A+L/da/B2JGwwAfI=; b=IzOBQCP3BwuT1fObM5IXUBjRAuVvWWf7hZ2Yjye1Anz1hZTHEtzx76WSUQC6F8Kp41 h0EUdrirpEPyYrPq9fsVSUy6pCiuU+bTozffw2HoDW7FEifs0fywAl6wL65A5AV3v2do UlwMUzU7bnEgeo2DEOAWZkQ2ZYjbceTGfdAImEMfJUVl4BUe4UnT0eb8Xazvh+UTjVYw oOFEzHBihJtXKZp7QU7mLGdwYv6A8VuwVn97POvLsL88MdMKqpkdiFLBfAM1Mg3O7K3v B2DBlEGr82jbGwrpX28fdsLqMuVseflO6yUzErjD64B/Fzh1KRgL2ybPUQridkKdecD0 krMw== X-Gm-Message-State: ANoB5pmnWoFhNDlYke5fFTEjXxUeIF3cR+tyoihdTyc3bvrPw+fzmMBB anvD6TR3ZMubHMkmrrM4NdNFqIjTdsGm19zduOo= X-Google-Smtp-Source: AA0mqf7K3C/o1DUvfHnSMEjjLphPhRxKiD7X7ByAz7w+sygk5m+oeteM5ukh2P167QSsx4go5gPPbAr97gf9PXgb/Z4= X-Received: by 2002:a05:620a:f0f:b0:6fa:df0:f326 with SMTP id v15-20020a05620a0f0f00b006fa0df0f326mr19212259qkl.23.1668601078911; Wed, 16 Nov 2022 04:17:58 -0800 (PST) MIME-Version: 1.0 References: <20221110195732.1382314-1-wusamuel@google.com> <880b7332-562c-4934-4e92-493b112568c9@arm.com> In-Reply-To: <880b7332-562c-4934-4e92-493b112568c9@arm.com> From: "Rafael J. Wysocki" Date: Wed, 16 Nov 2022 13:17:47 +0100 Message-ID: Subject: Re: [PATCH v1] Revert "cpufreq: schedutil: Move max CPU capacity to sugov_policy" To: Lukasz Luba Cc: Saravana Kannan , Sam Wu , "Rafael J. Wysocki" , Viresh Kumar , Ingo Molnar , Peter Zijlstra , Juri Lelli , Vincent Guittot , Dietmar Eggemann , Steven Rostedt , Ben Segall , Mel Gorman , Daniel Bristot de Oliveira , Valentin Schneider , "Isaac J . Manjarres" , kernel-team@android.com, "Rafael J. Wysocki" , linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 16, 2022 at 12:43 PM Lukasz Luba wrote: > > > > On 11/15/22 22:35, Saravana Kannan wrote: > > On Thu, Nov 10, 2022 at 11:57 AM Sam Wu wrote: > >> > >> This reverts commit 6d5afdc97ea71958287364a1f1d07e59ef151b11. > >> > >> On a Pixel 6 device, it is observed that this commit increases > >> latency by approximately 50ms, or 20%, in migrating a task > >> that requires full CPU utilization from a LITTLE CPU to Fmax > >> on a big CPU. Reverting this change restores the latency back > >> to its original baseline value. > >> > >> Fixes: 6d5afdc97ea7 ("cpufreq: schedutil: Move max CPU capacity to sugov_policy") > >> Cc: Lukasz Luba > >> Cc: Saravana Kannan > >> Cc: Isaac J. Manjarres > >> Signed-off-by: Sam Wu > > > > Rafael, can we pick this up please? > > > > Lukasz, no objections to the idea itself, but it's causing regression > > and we'd like to revert and then fix it. > > If you see this in mainline kernel, then I'm fine with reverting it. OK, I'll wait for the confirmation of this. > Then I will have to trace why this CPU capacity value can change over > time in mainline kernel (while it shouldn't, because we register the > cpufreq policy and the governor later, after we calculate the capacity > in arch_topology.c). Maybe something has changed in mainline in the > meantime in this CPU capacity setup code, which caused this side effect. > > I know that android-mainline has some different setup code for those > custom vendor governors. I just want to eliminate this bit and be on the > same page.