From patchwork Wed Dec 13 09:53:20 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Viresh Kumar X-Patchwork-Id: 121730 Delivered-To: patch@linaro.org Received: by 10.140.22.227 with SMTP id 90csp5257561qgn; Wed, 13 Dec 2017 01:55:53 -0800 (PST) X-Google-Smtp-Source: ACJfBot0wv4KMqTLDY3yhM227h2ACKIVnbPZLczVN/vu74GpMY2jaIkN7Swwew693oiIr8T0IA/6 X-Received: by 10.159.218.143 with SMTP id w15mr5547273plp.38.1513158952844; Wed, 13 Dec 2017 01:55:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1513158952; cv=none; d=google.com; s=arc-20160816; b=gazCOo9x50v6zUd89gdItBEhDMoZQUq4Lpll41E7ED8Eknh4TNxksrehcA91c3+ply FnbyuaZ/Vf4wol2A9ZyAdrH+FXhmt46YfJ/3iBBWLEJDd7GaNcDFyBrky7p70OhY0s0a yB9UPACFxa42ORYNvZpEtvNGKDey9dWjOa2rEGBRAtpMuqTetE5655AvpDXXcKcv9HZs nWUt+5OGUUMC+PVBUKYi+CFURMrWOeoKq16X4ocA1auBevjugN7P5yc16rGXxPKUDkVo 8RdX9q7MCFxZjxXse4j86B8lj8f+crLnvxmombEhuWWEUpDPBOerWgLJsFx3lPxcMYk2 Ujqw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:references :in-reply-to:message-id:date:subject:cc:to:from:dkim-signature :arc-authentication-results; bh=kKjnF/kCYI8xHDD/6GJGan6O1Vda+TONCV3Nbh/y2W0=; b=Exsy0AuVRNG/X8zMTWjSy6vS49fKe4aKr9AnBdB6IP2Ih/YN6Bf1VOq6SWz4wcpBBV Fo1BM3bUKfpQCDPmReixsijcjZFONL29t6dpVisJ77MiA0aZXLd6O/ACR+H4LSAJOEU1 aXWBXlR3v62kqSBXvOfl3G0+V3fQaVu2nD9EjmZSUnhlhFW0FENYYUT8drOuK5BDMDLL LAR4giQzFT14L+xbVo5oT5N0enx3NRFtimc0p5gUOmGry5QaDw8LNI+pMSSk3MWoJVpE Rw8A8I7DlnRgWg8c6Lgv/LrGW1rL2xzEJZE2KFXgovuQPp1UB3qwbD5vNgjxw0FnBE/0 awDw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=J7xZM4tJ; spf=pass (google.com: best guess record for domain of linux-pm-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-pm-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s189si1013128pgb.104.2017.12.13.01.55.52; Wed, 13 Dec 2017 01:55:52 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-pm-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=J7xZM4tJ; spf=pass (google.com: best guess record for domain of linux-pm-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-pm-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751076AbdLMJzv (ORCPT + 11 others); Wed, 13 Dec 2017 04:55:51 -0500 Received: from mail-pg0-f65.google.com ([74.125.83.65]:33312 "EHLO mail-pg0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752586AbdLMJxb (ORCPT ); Wed, 13 Dec 2017 04:53:31 -0500 Received: by mail-pg0-f65.google.com with SMTP id g7so1047627pgs.0 for ; Wed, 13 Dec 2017 01:53:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references :in-reply-to:references; bh=kKjnF/kCYI8xHDD/6GJGan6O1Vda+TONCV3Nbh/y2W0=; b=J7xZM4tJk4RjmHvXp7jUpl+L2NEBG2LBNOT3DFK+9FSff0sXZuUuUsLuD7f+mA+O4q fF2VO/RVoXQXQ2o5D4oQfqXNKEWCRHcsWlVjXVDoY0wrnRDMFlub3inaXzK4adCCuxlU 9vu5eKIRYhrOHhaYSlfCKdaCQUOzCylcnQCkY= 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:in-reply-to :references:in-reply-to:references; bh=kKjnF/kCYI8xHDD/6GJGan6O1Vda+TONCV3Nbh/y2W0=; b=onhjIGDIcU7F6zXkA13/oSc2RfuTZvr+bAued65X9v7fbX0sW9jkbSGDy2oBvM8B35 KUUY6bXjSUFsT1oY+sHF0vQQ0H6emnUkQcLSt7nWbtMFb371P/6hoc3qz4X1s6PrET5b ez+pxJFGfwKDXSEOVjbQNyQR7xdmR1RzdKmUsMYdpxiggKFdm73rfkWi6H7qQr5TJ4n8 VTtaNfI1ri0EzolUyvtIfUYrV5lzrH1ZUJmwbFFIAbtwWDXHEybEvVrNpbW+u8v0A/Nf RZcSCvoA8IKM4plvTlWhLABMFVBB+G5uOjPv3Eq5ZIK4HRW2xTTCQ7nddmB0ISpK5Km3 ICRA== X-Gm-Message-State: AKGB3mI3bkuUKKTze+MWVBa78FAzACeSnkhGjk6kiC9J43bgJTviSNjq KWDeBY3/62QRZE/Iu7mvrodgqg== X-Received: by 10.98.65.84 with SMTP id o81mr1647022pfa.55.1513158811234; Wed, 13 Dec 2017 01:53:31 -0800 (PST) Received: from localhost ([122.172.99.7]) by smtp.gmail.com with ESMTPSA id l21sm2551816pgc.76.2017.12.13.01.53.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Dec 2017 01:53:30 -0800 (PST) From: Viresh Kumar To: Rafael Wysocki , Ingo Molnar , Peter Zijlstra Cc: Viresh Kumar , linux-pm@vger.kernel.org, Vincent Guittot , dietmar.eggemann@arm.com, morten.rasmussen@arm.com, juri.lelli@redhat.com, tkjos@android.com, joelaf@google.com, linux-kernel@vger.kernel.org Subject: [PATCH 1/4] cpufreq: schedutil: Initialize sg_cpu->flags to 0 Date: Wed, 13 Dec 2017 15:23:20 +0530 Message-Id: <763feda6424ced8486b25a0c52979634e6104478.1513158452.git.viresh.kumar@linaro.org> X-Mailer: git-send-email 2.15.0.194.g9af6a3dea062 In-Reply-To: References: In-Reply-To: References: Sender: linux-pm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org 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. Change-Id: I028dbb40c5c242cff52fe1b14aeaff37f29a2f8d Signed-off-by: Viresh Kumar --- kernel/sched/cpufreq_schedutil.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- 2.15.0.194.g9af6a3dea062 Reviewed-by: Juri Lelli diff --git a/kernel/sched/cpufreq_schedutil.c b/kernel/sched/cpufreq_schedutil.c index 2f52ec0f1539..e8ccfa30f01a 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; }