From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934224AbeAJMTA (ORCPT + 1 other); Wed, 10 Jan 2018 07:19:00 -0500 Received: from terminus.zytor.com ([65.50.211.136]:35043 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932430AbeAJMS7 (ORCPT ); Wed, 10 Jan 2018 07:18:59 -0500 Date: Wed, 10 Jan 2018 04:15:09 -0800 From: tip-bot for Viresh Kumar Message-ID: Cc: peterz@infradead.org, juri.lelli@redhat.com, tglx@linutronix.de, mingo@kernel.org, vincent.guittot@linaro.org, viresh.kumar@linaro.org, hpa@zytor.com, linux-kernel@vger.kernel.org, rjw@rjwysocki.net, torvalds@linux-foundation.org Reply-To: mingo@kernel.org, vincent.guittot@linaro.org, viresh.kumar@linaro.org, hpa@zytor.com, torvalds@linux-foundation.org, linux-kernel@vger.kernel.org, rjw@rjwysocki.net, peterz@infradead.org, juri.lelli@redhat.com, tglx@linutronix.de In-Reply-To: <763feda6424ced8486b25a0c52979634e6104478.1513158452.git.viresh.kumar@linaro.org> References: <763feda6424ced8486b25a0c52979634e6104478.1513158452.git.viresh.kumar@linaro.org> To: linux-tip-commits@vger.kernel.org Subject: [tip:sched/core] sched/cpufreq: Initialize sg_cpu->flags to 0 Git-Commit-ID: 6257e7047890084fbeeb84c641200b43f0668abc X-Mailer: tip-git-log-daemon Robot-ID: Robot-Unsubscribe: Contact to get blacklisted from these emails MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: Commit-ID: 6257e7047890084fbeeb84c641200b43f0668abc Gitweb: https://git.kernel.org/tip/6257e7047890084fbeeb84c641200b43f0668abc Author: Viresh Kumar AuthorDate: Wed, 13 Dec 2017 15:23:20 +0530 Committer: Ingo Molnar CommitDate: Wed, 10 Jan 2018 11:30:29 +0100 sched/cpufreq: Initialize sg_cpu->flags to 0 Initializing sg_cpu->flags to SCHED_CPUFREQ_RT has no obvious benefit. The flags field wouldn't be used until the utilization update handler is called for the first time, and once that is called we will overwrite flags anyway. Initialize it to 0. Signed-off-by: Viresh Kumar Signed-off-by: Peter Zijlstra (Intel) Reviewed-by: Juri Lelli Cc: Linus Torvalds Cc: Peter Zijlstra Cc: Rafael Wysocki Cc: Thomas Gleixner Cc: Vincent Guittot Cc: dietmar.eggemann@arm.com Cc: joelaf@google.com Cc: morten.rasmussen@arm.com Cc: tkjos@android.com Link: http://lkml.kernel.org/r/763feda6424ced8486b25a0c52979634e6104478.1513158452.git.viresh.kumar@linaro.org Signed-off-by: Ingo Molnar --- kernel/sched/cpufreq_schedutil.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/sched/cpufreq_schedutil.c b/kernel/sched/cpufreq_schedutil.c index d6717a3..22d4630 100644 --- a/kernel/sched/cpufreq_schedutil.c +++ b/kernel/sched/cpufreq_schedutil.c @@ -655,7 +655,7 @@ static int sugov_start(struct cpufreq_policy *policy) memset(sg_cpu, 0, sizeof(*sg_cpu)); sg_cpu->cpu = cpu; sg_cpu->sg_policy = sg_policy; - sg_cpu->flags = SCHED_CPUFREQ_RT; + sg_cpu->flags = 0; sg_cpu->iowait_boost_max = policy->cpuinfo.max_freq; }