Received: by 2002:ac0:aed5:0:0:0:0:0 with SMTP id t21csp4210748imb; Wed, 6 Mar 2019 07:58:08 -0800 (PST) X-Google-Smtp-Source: APXvYqzUOSs1snpqMp5xdIyVZYL7S5t82bWUFRJLzzZ1X+Gw+Tz7zv6yqTLT6VfOPvQCfnmHOfIq X-Received: by 2002:a62:4e8a:: with SMTP id c132mr7794442pfb.24.1551887888670; Wed, 06 Mar 2019 07:58:08 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551887888; cv=none; d=google.com; s=arc-20160816; b=tpoOA4MDvss0LQbP6OXL76LkP8kLJh6lYalBB33Q11Z+KlN2/BVjVbPeWq5XO6m+YA Rjh+izBat2m6Ja63aONBSqcgY+RQxNwHAuNhJ8h6Ypb6+3/GScda9U/Q8cqONvNFSSGq T/KWUuhIvCF4C6HVijr70CeosYJsLryZgbPpHzo/0NMuE28AyQwFRSkaaG8GBjK/j8iW VBo8I0Yz8HQO2bp8ocDf8NFe5jLwUiNS7bgJO04k2g1vTv766bn1qtlMBpjEE09P7a0k zyDAiJgOnqOu8mcOOpCdvNhvCuiEluQbOKb/DQs15fpy+TlAridUREp3dcQZbBcCieGz 4gWQ== 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:message-id:date :subject:cc:to:from:dmarc-filter:dkim-signature:dkim-signature; bh=FGNyl7tBwIV4peSkzs/xcQOX8hKxrm4edkvazv8nGV8=; b=jD5Sx4u7kJ8R/jkuDtMwqStQ3NApzUV2wZZRekjqmNhZ5o0vd6c2xCiXVP+woWQCPu 4fzFB8jsLK31Cv0UpvCvRamaFjqzAW38gl3ga3UfHwl5/2D5sL9O0S/F5d/A3Qse2Lux i2f88ujvxhPpT9Ap0LQW3aXNoNyiD5MQYSfEYRkrMOlRaGc8VwGDWXG4Ezw5ueUy7h0/ 2p7+nxz20qcCbkBZyzebR7pILm/ggDahN0hMfP6MLMGUpk6ysaph//EPzYCsQDyQ89bm rq9tz3MnT6Mb4hdYMXVLzU/rNmwIONvkb4G6GUdaAc666ENWONXvEpAsIE+zgL3D6JHK XBzw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=H83DSUY7; dkim=pass header.i=@codeaurora.org header.s=default header.b=mm0e27pQ; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x64si1905476pfx.156.2019.03.06.07.57.53; Wed, 06 Mar 2019 07:58:08 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-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=@codeaurora.org header.s=default header.b=H83DSUY7; dkim=pass header.i=@codeaurora.org header.s=default header.b=mm0e27pQ; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728322AbfCFP2c (ORCPT + 99 others); Wed, 6 Mar 2019 10:28:32 -0500 Received: from smtp.codeaurora.org ([198.145.29.96]:46008 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726877AbfCFP2c (ORCPT ); Wed, 6 Mar 2019 10:28:32 -0500 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id 58ECB60ACE; Wed, 6 Mar 2019 15:28:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1551886111; bh=lr6xzu7kGN76YrY51OX5vOavA1Q3p7mxTgffMhP+ox0=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=H83DSUY77oPss5VUyyo+KFapYjzCsy/ioaSv8+Fw7LMCDgMkSWlD0fS9KEAHZR46N XFWA6FS4mRSpCXzAF3FLqtIxu09FPW7KJC3gCIjb7rVp08s+rqeynaXjbLfSbUDfwa i4Hi4RiB4z67p8Lbwsbs67beIQWntTIiMbR8gPiM= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on pdx-caf-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=2.0 tests=ALL_TRUSTED,BAYES_00, DKIM_INVALID,DKIM_SIGNED autolearn=no autolearn_force=no version=3.4.0 Received: from lingutla-linux.qualcomm.com (blr-c-bdr-fw-01_globalnat_allzones-outside.qualcomm.com [103.229.19.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: clingutla@smtp.codeaurora.org) by smtp.codeaurora.org (Postfix) with ESMTPSA id 23CD9606AC; Wed, 6 Mar 2019 15:28:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1551886109; bh=lr6xzu7kGN76YrY51OX5vOavA1Q3p7mxTgffMhP+ox0=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=mm0e27pQEdQJuqopTnGW1Bv4oOsAR7xsjC/BMwWPaIk/JrrR4GsoQTMgbSWsZQqsg daOiV/I6pRlHwGXTNe5NcP7b4o1pgfH3tCEpnAtHji79rlEA4aQK1/n7d5GAPdcDQq 1/Ig6bKBge2GYx+hvbhr/p5zC5OBLWcQN5DAbpAk= DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 23CD9606AC Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=clingutla@codeaurora.org From: Lingutla Chandrasekhar To: quentin.perret@arm.com, sudeep.holla@arm.com, dietmar.eggemann@arm.com, gregkh@linuxfoundation.org Cc: will.deacon@arm.com, catalin.marinas@arm.com, morten.rasmussen@arm.com, linux-arm-kernel@lists.infradead.org, jeremy.linton@arm.com, linux-kernel@vger.kernel.org, Lingutla Chandrasekhar Subject: [PATCH v1] arch_topology: Make cpu_capacity sysfs node as ready-only Date: Wed, 6 Mar 2019 20:57:53 +0530 Message-Id: <1551886073-16217-1-git-send-email-clingutla@codeaurora.org> X-Mailer: git-send-email 2.7.4 In-Reply-To: <20190306152254.GB19434@e105550-lin.cambridge.arm.com> References: <20190306152254.GB19434@e105550-lin.cambridge.arm.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org If user updates any cpu's cpu_capacity, then the new value is going to be applied to all its online sibling cpus. But this need not to be correct always, as sibling cpus (in ARM, same micro architecture cpus) would have different cpu_capacity with different performance characteristics. So updating the user supplied cpu_capacity to all cpu siblings is not correct. And another problem is, current code assumes that 'all cpus in a cluster or with same package_id (core_siblings), would have same cpu_capacity'. But with commit '5bdd2b3f0f8 ("arm64: topology: add support to remove cpu topology sibling masks")', when a cpu hotplugged out, the cpu information gets cleared in its sibling cpus. So user supplied cpu_capacity would be applied to only online sibling cpus at the time. After that, if any cpu hot plugged in, it would have different cpu_capacity than its siblings, which breaks the above assumption. So instead of mucking around the core sibling mask for user supplied value, use device-tree to set cpu capacity. And make the cpu_capacity node as read-only to know the assymetry between cpus in the system. Signed-off-by: Lingutla Chandrasekhar --- drivers/base/arch_topology.c | 33 +-------------------------------- 1 file changed, 1 insertion(+), 32 deletions(-) diff --git a/drivers/base/arch_topology.c b/drivers/base/arch_topology.c index edfcf8d..d455897 100644 --- a/drivers/base/arch_topology.c +++ b/drivers/base/arch_topology.c @@ -7,7 +7,6 @@ */ #include -#include #include #include #include @@ -51,37 +50,7 @@ static ssize_t cpu_capacity_show(struct device *dev, static void update_topology_flags_workfn(struct work_struct *work); static DECLARE_WORK(update_topology_flags_work, update_topology_flags_workfn); -static ssize_t cpu_capacity_store(struct device *dev, - struct device_attribute *attr, - const char *buf, - size_t count) -{ - struct cpu *cpu = container_of(dev, struct cpu, dev); - int this_cpu = cpu->dev.id; - int i; - unsigned long new_capacity; - ssize_t ret; - - if (!count) - return 0; - - ret = kstrtoul(buf, 0, &new_capacity); - if (ret) - return ret; - if (new_capacity > SCHED_CAPACITY_SCALE) - return -EINVAL; - - mutex_lock(&cpu_scale_mutex); - for_each_cpu(i, &cpu_topology[this_cpu].core_sibling) - topology_set_cpu_scale(i, new_capacity); - mutex_unlock(&cpu_scale_mutex); - - schedule_work(&update_topology_flags_work); - - return count; -} - -static DEVICE_ATTR_RW(cpu_capacity); +static DEVICE_ATTR_RO(cpu_capacity); static int register_cpu_capacity_sysctl(void) { -- QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project.