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 X-Spam-Level: X-Spam-Status: No, score=-4.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_GIT autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 93A15C0650E for ; Mon, 1 Jul 2019 11:26:27 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6CA32206A3 for ; Mon, 1 Jul 2019 11:26:27 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="CMuYzAoc" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728438AbfGAL00 (ORCPT ); Mon, 1 Jul 2019 07:26:26 -0400 Received: from mail-pf1-f193.google.com ([209.85.210.193]:37015 "EHLO mail-pf1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727239AbfGAL0Z (ORCPT ); Mon, 1 Jul 2019 07:26:25 -0400 Received: by mail-pf1-f193.google.com with SMTP id 19so6446430pfa.4 for ; Mon, 01 Jul 2019 04:26:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=ynBBs/NOZX3NzX0Q9+1BmT1OjndcQg2QjZPTWCNOFLQ=; b=CMuYzAocf2wKTBA+GXQccgtp+dOADRGiyab8LzNK8mpqZGI8+ekJbNSqjuhfGczRbq hIyzHyq/PiHMbripC+nQ6rGz1xIto5k8YmbZ/QToU1+wA38o0NOtwV3vN3FydQ4oJlJ6 DeZhtBv1ma2z613Udb89826z95GgCHsVy8x4RgAmIpmJhpBJLGz0pX00h/+sWQdBCx+w 3YIBy8CkySQxBodv1KAwNRBYE80ptRyiunQwNu6lrXoQgRyhzccdr1ApGHHHMeJp+Pav Fa9gc2WB04WtnC4y4X8rGtcSZtpzJGVJMrUKnzxjWLd435YOtIXQjYJcMceDY3iumXWQ /n7g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=ynBBs/NOZX3NzX0Q9+1BmT1OjndcQg2QjZPTWCNOFLQ=; b=KWiLfDmJpxpxcbIl8+Wb7kQwSrfO0oUy7oGgUI/cY/K/Afi7iVXRlyc0uQdCTpcHr2 4OUwbdLAWAG4E+3nfRvt3MOW91YxUHmcmMzPpDZTxB4IS2lcXnz6iZYRB/ldq2mqegTU pbMWKclkE+ln5WjN45gtyJCDWbi2x2oOor45LeqSjML9Aw8/UJMPTnr04Hy953+32ojP RtBt9fa0iYOEQW+WDlkhqJxlRVZXcnNYc2VsS7FhQ/Zuisb28grVTpEAiz3uAMJGuDAk YF/hKTGydREv2pzVJsVRuyourkGvAxLH5p1eJrIcOXQeFT84SdhN6zeWDsZOsbiJZPRT Pgkw== X-Gm-Message-State: APjAAAVVDiOJpUV0hF5EhUdyiOxkzD4jA8lfXc4rK5L0gYB3GZVBWSuy YI5x7U+q+z4j9vxzyVMdpyR1EA== X-Google-Smtp-Source: APXvYqygZ3fAikMt9o/P/XbZtlOuA1YA0A6ZN7tJAAFjFS+dwZF9vKO/IVT+6FQ6twYmXoNi+aXWPQ== X-Received: by 2002:a17:90a:33c4:: with SMTP id n62mr31355142pjb.28.1561980383274; Mon, 01 Jul 2019 04:26:23 -0700 (PDT) Received: from localhost ([122.172.21.205]) by smtp.gmail.com with ESMTPSA id i9sm8248146pgo.46.2019.07.01.04.26.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 01 Jul 2019 04:26:22 -0700 (PDT) From: Viresh Kumar To: Rafael Wysocki , Daniel Lezcano , Kevin Hilman , Len Brown , Len Brown , Pavel Machek , Srinivas Pandruvada , Ulf Hansson Cc: Viresh Kumar , linux-pm@vger.kernel.org, Vincent Guittot , Qais.Yousef@arm.com, mka@chromium.org, juri.lelli@gmail.com, linux-kernel@vger.kernel.org Subject: [PATCH V5 0/7] cpufreq: Use QoS layer to manage freq-constraints Date: Mon, 1 Jul 2019 16:56:08 +0530 Message-Id: X-Mailer: git-send-email 2.21.0.rc0.269.g1a574e7a288b MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, This patchset attempts to manage CPU frequency constraints using the PM QoS framework. It only does the basic stuff right now and moves the userspace constraints to use the QoS infrastructure. Todo: - Migrate all users to the QoS framework and get rid of cpufreq specific notifiers. - Make PM QoS learn about the relation of CPUs in a policy, so a single list of constraints is managed for all of them instead of per-cpu constraints. V4->V5: - A new patch added, 6/7. V3->V4: - Few commit logs updated as suggested during reviews. - Separate commit (2/6) to create resume-latency specific routines - Reused earlier work ("update") for notifiers as well. - Kept Reviewed-by tags as is as the patches normally got better only. Please take them back if you find any issues. V2->V3: - Add a comment in cpufreq.c as suggested by Qais. - Rebased on latest pm/linux-next. V1->V2: - The previous version introduced a completely new framework, this one moves to PM QoS instead. - Lots of changes because of this. -- viresh [1] http://lore.kernel.org/lkml/cover.1560999838.git.viresh.kumar@linaro.org Viresh Kumar (7): PM / QOS: Pass request type to dev_pm_qos_{add|remove}_notifier() PM / QOS: Rename __dev_pm_qos_read_value() and dev_pm_qos_raw_read_value() PM / QOS: Pass request type to dev_pm_qos_read_value() PM / QoS: Add support for MIN/MAX frequency constraints cpufreq: Register notifiers with the PM QoS framework cpufreq: intel_pstate: Reuse refresh_frequency_limits() cpufreq: Add QoS requests for userspace constraints Documentation/power/pm_qos_interface.txt | 12 +- drivers/base/power/domain.c | 8 +- drivers/base/power/domain_governor.c | 4 +- drivers/base/power/qos.c | 135 +++++++++++++-- drivers/base/power/runtime.c | 2 +- drivers/cpufreq/cpufreq.c | 201 ++++++++++++++++------- drivers/cpufreq/intel_pstate.c | 7 +- drivers/cpuidle/governor.c | 2 +- include/linux/cpufreq.h | 12 +- include/linux/pm_qos.h | 48 ++++-- 10 files changed, 320 insertions(+), 111 deletions(-) -- 2.21.0.rc0.269.g1a574e7a288b