Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp2653761pxj; Mon, 17 May 2021 06:49:16 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxWdVXup2zLCXD3c1U6TGd6Rve9/qHob8RBZApZk17ulpVxLtmjhrjpHB5T/HRoaeXVW215 X-Received: by 2002:a17:906:938a:: with SMTP id l10mr1857ejx.540.1621259356351; Mon, 17 May 2021 06:49:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1621259356; cv=none; d=google.com; s=arc-20160816; b=D2KVCCnhSZLGGyWCMmulkIcVLyt3LrDZV+q6/r+wbsp0x9hWZFeGZOZNPYHjfXEay0 LY2Co+EbspAov9HC5sxdQlsObWiG5kLuM18QVGQ1jFlD3OyvPwO6fTChUDltbg6XFI8g mGnkOzjNyotuQNDuXGkKJ4uDz1yFWD9EzG25L+UKBhPuRttindB51rtwrJ+GuDj0doBZ +o7GZb492gHd9MyIRRIywSdCWqazW2ZT0+4XME+LPsFLRtNOACbKv+hD1V+rdImxmCRf BwtuORpBxxz6eoP7o5T8SH5Uld5e53cE2nk3XVtr31sW8sSmGngikt5JGS71m9opNFFn Yt9w== 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=h5QzNp14J3j6W5e/bZLzGJnsFQviWAmflPRKn1kyoyM=; b=mpB7IKeYVamzFd6jiMZQIlMWMgVRb9sSdelnxdL8H8XMh0iFuN/CAPTOj1r03zCVFw quMfheA3T5leJuTPKOZe4GSebFIuTEAZ/T20dSBRX/0ccqNRACVrjFJfQK0cQai9TbEL TZjsQjSwzrTSJgTuHcj50WDFBONtSOQXnogT7lB14t7z+iy3Fk6H1GuTv44Q8UzXvnbM JY4UmAYHDjFRFy5E7agE/QouhBwJiGqmUAMb4jG7XNiHD0XhvNVqrXWGswQGKmVTo3Nm SClINLPzW5lpD+tf25/iSbumcD1ipE2NVCNvvH2huizVCM3NMXa6M6pvt0TlU+MQTD5q DPZA== 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 q1si15111391ejy.298.2021.05.17.06.48.51; Mon, 17 May 2021 06:49:16 -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 S235537AbhEQI0B (ORCPT + 99 others); Mon, 17 May 2021 04:26:01 -0400 Received: from foss.arm.com ([217.140.110.172]:45194 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235248AbhEQIZz (ORCPT ); Mon, 17 May 2021 04:25:55 -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 C7399106F; Mon, 17 May 2021 01:24:39 -0700 (PDT) Received: from e113131-lin.cambridge.arm.com (e113131-lin.cambridge.arm.com [10.1.195.76]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPA id 76DFD3F719; Mon, 17 May 2021 01:24:38 -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 v4 3/3] sched/doc: Update the CPU capacity asymmetry bits Date: Mon, 17 May 2021 09:23:51 +0100 Message-Id: <1621239831-5870-4-git-send-email-beata.michalska@arm.com> In-Reply-To: <1621239831-5870-1-git-send-email-beata.michalska@arm.com> References: <1621239831-5870-1-git-send-email-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 9b7cbe4..805f85f 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 afe02d3..8fbce5e 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.7.4