Received: by 2002:a25:ca44:0:0:0:0:0 with SMTP id a65csp2457973ybg; Thu, 30 Jul 2020 23:17:31 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwtsr0mWGX0mZEixjNst4ES5Z7Ou09jSJlvda/hZ2Tqq+GOg9eT6DCN3iGRiqyewx9hXNmX X-Received: by 2002:a50:e705:: with SMTP id a5mr2400347edn.345.1596176250843; Thu, 30 Jul 2020 23:17:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1596176250; cv=none; d=google.com; s=arc-20160816; b=NU0qef3dO6X22ipnUn2jNVjBWhgyXvFEEYJMjBKo6/tSYhbXN7RzFMSUWoM/DZMyFa lh/am+pHltcClzIjB8/rKgu81KgjWK+h3Hg5EOjqJM17nXW6R2H5IGcN2H6Nmk8q1Yci lJvhTyJfWDUQB6+dXSShtnxY+OKDD4ulSUifamZhgIXzV46inLcvk9CcDIrBze3Tdfg+ cKGaU21+cSrJ0hx82ooib+gqMoodkonX/YPtr/k+fdKBzvhSpelTs8KMrCRNRRxBgDFv /ZzmmSbw6CWNNL9vRs5NKxMk2ZXDFwL4cbM4cVJ2MwDB1+AvTewqQrC7oA4v+/xcxle5 x6Lw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=PLQTsE4NugPi++RkdPG8HrcyiFj1RcJPX6rjR0GyY9o=; b=PUGoX6kUL9vNvLZMEIO0hy+bKbxNEcYhUSAT/O55ZLzqcodrQB3ieToiAffEmqxoj7 3QLsJW/l5KBeq0zJsDuHDsa4n0Ax40IBngc5v0J9Zo8vK9vwQYqUBuO8SO9uFU5NPVwY 75L5Cysl7/TPUH64o/jo0wmij/Q3CPsJUrZv156BPYMNiAlV6WzyzCatsrCAuLBb7MPX QGoFa0/KJOjcgKpk6L+wFw1zLxxgrI8NdjPmM0AMfNuZnkYJQ6gfhl9rTZQ6R0fun8F1 v+pxQybEKwwAPGIoLc4zueYGB50y4aycLE2p4vcYXg9b7/aGz/j6ZsAPjy8eC5ngIGQT zlrA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=OI5lVO20; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id dr6si5794775ejc.638.2020.07.30.23.16.55; Thu, 30 Jul 2020 23:17:30 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=OI5lVO20; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731312AbgGaGQs (ORCPT + 99 others); Fri, 31 Jul 2020 02:16:48 -0400 Received: from mail.kernel.org ([198.145.29.99]:47746 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731152AbgGaGQs (ORCPT ); Fri, 31 Jul 2020 02:16:48 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id D272F20663; Fri, 31 Jul 2020 06:16:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1596176207; bh=WHR8jRh3qw/PGsoIxzFulqDz9Zu+JVeoIc2MSsUYN/M=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=OI5lVO20EM3bWyyFImTT9FJvGHHPbgWeedyvuONmw7eQzwK2guodFYtmM8wMtPQo7 84E9DviWGEsGT/vuijIg0pZsD91cb3fTYtBZzPAsf09vLA3IFwP3MyIMVuZC5x4YES PRf7eWSVxUIqpW41z3Nb3Tm1G6btg7r5zEwIz+Do= Date: Fri, 31 Jul 2020 08:16:34 +0200 From: Greg KH To: Dongdong Yang Cc: rjw@rjwysocki.net, viresh.kumar@linaro.org, mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com, vincent.guittot@linaro.org, dietmar.eggemann@arm.com, rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de, devel@driverdev.osuosl.org, gulinghua@xiaomi.com, tanggeliang@xiaomi.com, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, yangdongdong@xiaomi.com, duhui@xiaomi.com, zhangguoquan@xiaomi.com, fengwei@xiaomi.com, taojun@xiaomi.com, rocking@linux.alibaba.com, huangqiwu@xiaomi.com Subject: Re: [PATCH] sched: Provide USF for the portable equipment. Message-ID: <20200731061634.GA1508201@kroah.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 30, 2020 at 09:35:42PM +0800, Dongdong Yang wrote: > From: Dongdong Yang > > This patch provides USF(User Sensitive Feedback factor) > auxiliary cpufreq governor to support high level layer > sysfs inodes setting for utils adjustment purpose from > the identified scenario on portable equipment. > Because the power consumption and UI response are more > cared for by portable equipment?users. And the "screen > off" status stands for no request from the user, however, > the kernel is still expected to notify the user in time > on modem, network or powerkey events occur. USF provides > "sched_usf_non_ux_r" sysfs inode to cut down the utils > from user space tasks according to high level scenario. > In addition, it usually hints more cpufreq demand that > the preemptive counts of the tasks on the cpu burst and > over the user expecting completed time such as the ratio > sysctl_sched_latency to sysctl_sched_min_granularity > on "screen on" status, which more likely with more UI. > The sysfs inodes "sched_usf_up_l0_r" and "sched_usf_down_r" > have been provided to adjust the utils according to high > level identified scenario to alloc the cpufreq in time. > > Dongdong Yang (1): > sched: Provide USF for portable equipment. > > drivers/staging/Kconfig | 2 + > drivers/staging/Makefile | 1 + > drivers/staging/fbsched/Kconfig | 10 ++ > drivers/staging/fbsched/Makefile | 2 + > drivers/staging/fbsched/usf.c | 351 +++++++++++++++++++++++++++++++++++++++ > kernel/sched/cpufreq_schedutil.c | 11 +- > 6 files changed, 376 insertions(+), 1 deletion(-) > create mode 100644 drivers/staging/fbsched/Kconfig > create mode 100644 drivers/staging/fbsched/Makefile > create mode 100644 drivers/staging/fbsched/usf.c For new staging drivers/code, we need a TODO file that lists what remains to be done on the code to get it out of staging/ I don't see any good reason why this has to go to staging now, what prevents it from being merged to the "real" part of the kernel today? thanks, greg k-h