Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp3291399pxj; Mon, 24 May 2021 03:19:22 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzNWTBr8aKfPNyDyPzSTsl7XptBHG59EvM9QrsDooBAoqmZjh7xBt5HKoaHmwh6x3EQcQDl X-Received: by 2002:a05:6402:10c9:: with SMTP id p9mr25025345edu.268.1621851562327; Mon, 24 May 2021 03:19:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1621851562; cv=none; d=google.com; s=arc-20160816; b=LoFhqlhDbBahfcYkAC7yH2gcYc9smQ54ewUBfBjotEWUN4X7XtC4SHNFzxFIutzV9O KReoW3gPvJbOG9FJtvHMrlM5OJpWNyR7INT9kmnjhTyVyqlZy4wQmbU7QBnslRCe2Imk iS/6naV8DCLYnh5JTvjS312HH+/qdOJMSuPBI0I4AzwOempWqOSrQITMdykwgpZWf1lX IET6RQwyBnZeC/Zo93/OXjyRWr3ams82A03D3TN88cmRdqZ/XMIFy8kVCwJmjKfKqkk3 /V1wV1E2GmACI9Z7LweYKwBrmN1Bb+WtDeLqYVUI1Xkzdypvmf44LOEkVkumw8qIptAN ufsQ== 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=HID8kkYBNZQxxDUcnFKGVmfiyV6BovUZce2osh4aNF+F1jL5EWqo23cBG9usJIJb/l R6yVKWmPec4Oud1POsf/hlJjgemeUwt2uomQ7IWLldyqA5sTyxYG3RY4PbrU8YQN3iok zL2WXdEd/Hs5RBJQp8DBbw/1NkiyCkaNQW15lWEgLPib7Fc8Fm6x29ma3eVp104r+EnD AslCdVuazrpd1xpyhJqVK+XgZUY/KO6ACLl0mWLXtUagVsR9Po0wddfO8QwBClS2nN7G NbDuWaGCxK3eHQ4juzThENzklcwCJMTqJea+HUkJspIpo/uhaQ3Eo3hXIWQgPQH08GyR jCsQ== 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 t7si11263187edw.434.2021.05.24.03.18.59; Mon, 24 May 2021 03:19:22 -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 S232602AbhEXKS1 (ORCPT + 99 others); Mon, 24 May 2021 06:18:27 -0400 Received: from foss.arm.com ([217.140.110.172]:40540 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232587AbhEXKSW (ORCPT ); Mon, 24 May 2021 06:18:22 -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 ED2D231B; Mon, 24 May 2021 03:16:54 -0700 (PDT) Received: from e120325.arm.com (unknown [10.57.84.138]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPA id 77D973F719; Mon, 24 May 2021 03:16:53 -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 v5 3/3] sched/doc: Update the CPU capacity asymmetry bits Date: Mon, 24 May 2021 11:16:17 +0100 Message-Id: <20210524101617.8965-4-beata.michalska@arm.com> In-Reply-To: <20210524101617.8965-1-beata.michalska@arm.com> References: <20210524101617.8965-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