Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp743856pxj; Thu, 27 May 2021 10:34:49 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz2/NbqSF0DrIagT7ApguPKhjkFGrFAkSoTQgCfRPk9iqs98wVD8kovuK6k2XckHJxqdmFH X-Received: by 2002:a05:6e02:be8:: with SMTP id d8mr3952826ilu.63.1622136889362; Thu, 27 May 2021 10:34:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1622136889; cv=none; d=google.com; s=arc-20160816; b=ndFVaLyYBfEvk1AMyTJ/EZAPj+fddOf7HTJ3M01+hJf0hQILJzcdBDxwLPvbXAcuhV f30k9YaGUXws/MduXVdl4xtDkK3wXIO5cm9Ixz6D2EEcGTFVG4v0C7mS+41CtraHiTJ0 RKMFBJ+os8vLCramU822jt4C0ACihGpCAtKS0kLAAlSIQLhpG0M6OqAdUoG73K9xJDn0 tzRE3x/2sjKeVxikkmiLmLFYuc86YzM+pQ7ar5CsG8vU9QOSgS9sxUAten2Toxq3ko0o c7YpC8u4B7nnWqzRnH9TI7VZz5GIFUUm5Wnsn+3cNL7Fd2/tgRRskFW9bMKFPo8OwJob /8hg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:references:in-reply-to:message-id:date:subject :cc:to:from; bh=RFK2fVGtwlCR3iFZE/1NLO8g+3Omtj296lFcodGeyYw=; b=vZdQ03rmKozKIW+LIlBdpdAjgDcjRcNja5Qtc8EnQ69Bv1QMpZZNSyPNlewRzSf2vn 7o2mCWOX61XRSnHyEAO0C5p2BQX33+oDUlRCnc+xHp4/KHFDFhrFr9UNoClGSIIgVai3 cGZgLJFfhln5yQmcG4C7T9feJBFvT9OCSHqGASsA1y+INE7jpRDR+Err1pttgfH5cecF EmqXMI5GGnQ7aHhn5r8L7w5JYcjyu/9dD3HCcwvbpGMqeRGoMdPOqTiDB/f20w510iWP ZYH8i0zklol04XVWNbStRjqpJmyccAiKzWmJufy1KIl4CJcr6zLOKkTnqOakchLBXuxK L0NA== ARC-Authentication-Results: i=1; mx.google.com; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id s8si3008720ilt.116.2021.05.27.10.34.35; Thu, 27 May 2021 10:34:49 -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; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234618AbhE0Pku (ORCPT + 99 others); Thu, 27 May 2021 11:40:50 -0400 Received: from foss.arm.com ([217.140.110.172]:59524 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233848AbhE0Pkn (ORCPT ); Thu, 27 May 2021 11:40:43 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 67C6211D4; Thu, 27 May 2021 08:39:10 -0700 (PDT) Received: from e120325.arm.com (unknown [10.57.84.138]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPA id DCEF13F73B; Thu, 27 May 2021 08:39:08 -0700 (PDT) From: Beata Michalska To: linux-kernel@vger.kernel.org Cc: peterz@infradead.org, mingo@redhat.com, juri.lelli@redhat.com, vincent.guittot@linaro.org, valentin.schneider@arm.com, dietmar.eggemann@arm.com, corbet@lwn.net, rdunlap@infradead.org, linux-doc@vger.kernel.org Subject: [PATCH v6 3/3] sched/doc: Update the CPU capacity asymmetry bits Date: Thu, 27 May 2021 16:38:42 +0100 Message-Id: <20210527153842.17567-4-beata.michalska@arm.com> In-Reply-To: <20210527153842.17567-1-beata.michalska@arm.com> References: <20210527153842.17567-1-beata.michalska@arm.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Update the documentation bits referring to capacity aware scheduling with regards to newly introduced SD_ASYM_CPUCAPACITY_FULL sched_domain flag. Signed-off-by: Beata Michalska Reviewed-by: Valentin Schneider --- Documentation/scheduler/sched-capacity.rst | 6 ++++-- Documentation/scheduler/sched-energy.rst | 2 +- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/Documentation/scheduler/sched-capacity.rst b/Documentation/scheduler/sched-capacity.rst index 9b7cbe43b2d1..805f85f330b5 100644 --- a/Documentation/scheduler/sched-capacity.rst +++ b/Documentation/scheduler/sched-capacity.rst @@ -284,8 +284,10 @@ whether the system exhibits asymmetric CPU capacities. Should that be the case: - The sched_asym_cpucapacity static key will be enabled. -- The SD_ASYM_CPUCAPACITY flag will be set at the lowest sched_domain level that - spans all unique CPU capacity values. +- The SD_ASYM_CPUCAPACITY_FULL flag will be set at the lowest sched_domain + level that spans all unique CPU capacity values. +- The SD_ASYM_CPUCAPACITY flag will be set for any sched_domain that spans + CPUs with any range of asymmetry. The sched_asym_cpucapacity static key is intended to guard sections of code that cater to asymmetric CPU capacity systems. Do note however that said key is diff --git a/Documentation/scheduler/sched-energy.rst b/Documentation/scheduler/sched-energy.rst index afe02d394402..8fbce5e767d9 100644 --- a/Documentation/scheduler/sched-energy.rst +++ b/Documentation/scheduler/sched-energy.rst @@ -328,7 +328,7 @@ section lists these dependencies and provides hints as to how they can be met. As mentioned in the introduction, EAS is only supported on platforms with asymmetric CPU topologies for now. This requirement is checked at run-time by -looking for the presence of the SD_ASYM_CPUCAPACITY flag when the scheduling +looking for the presence of the SD_ASYM_CPUCAPACITY_FULL flag when the scheduling domains are built. See Documentation/scheduler/sched-capacity.rst for requirements to be met for this -- 2.17.1