Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp306056pxj; Thu, 3 Jun 2021 07:11:25 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy4r/DW8aEKeVMj3/fmuR+jAEQ7h81GIkhEBcr8vxmKcFSbePVHwTL5jqpoc6XTQbbTnvU/ X-Received: by 2002:a05:6402:3444:: with SMTP id l4mr14977718edc.259.1622729485054; Thu, 03 Jun 2021 07:11:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1622729485; cv=none; d=google.com; s=arc-20160816; b=02cWFNFv04VuZiCHUN2cCNvKxi93wtI180DAl5rNrFVCzs1H9HcwNTqXXEw11BxTok JIYsXxrHw9iuhPOKrp06Psu2oJtJvsdLhNeK1FIv+1E8ET3cpUD1+3QkVH44VAa9xzvE ogvQu97sbb+70eaJM8rIzuYGTPjRlls/Anp0vKW94HCDGVhqSuiTvBuFX59Lv4Art2tU GNcCh9ZhOmZUrlqzBNAkS1V0cebxigbcb7+K6qX0SzEBdr1qsMTPxKgo/LGquXWnJYLp bvYWFCbG8Y40YaWbrIC0LpprhYLMfcVAE3WaFTlwz5ftm5fSQv2aSvjSNqBvDdySJs9d 8jZA== 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=saZ34JBzAH+r3xw7Z1JpTSHZRcLlUXirIPIsbvoQizI=; b=Px8RIhww8mpMEAxZXNx4GuAxO6tpHV68ynH9o1OB00Q8wx8bA0xhdOEMiJ5Ypu05su +smgN/jQyYHi3KUKRW5ystH1huDuP9aCAqNAnMfLE1wuTKrHiEmzlY8q9MJj0dGTBFvP /f6j7CUZr3KiHI9VvZAtDJv6QBQ+SQ83xnYxRWcV34u1kE1zAmnVAqdZ6qxDBPxa5s7P VWnairIg/jMgtK1JTOIsFSqkflMrwJo+1OgIyZJXLz7LA7G59c1AFP0Dae7RlSIfM6qu xMsDKakMd4wrAMRldoTAcj2JFaIEUNNdYVeYG4sc1XfLVyYVFN3tI9aDK1eI5KNIuXF0 W9dQ== 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 ga21si2440376ejb.24.2021.06.03.07.11.00; Thu, 03 Jun 2021 07:11:25 -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 S231574AbhFCOIs (ORCPT + 99 others); Thu, 3 Jun 2021 10:08:48 -0400 Received: from foss.arm.com ([217.140.110.172]:42282 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230114AbhFCOIs (ORCPT ); Thu, 3 Jun 2021 10:08:48 -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 6896011FB; Thu, 3 Jun 2021 07:07:03 -0700 (PDT) Received: from e120325.arm.com (unknown [10.57.85.170]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPA id 57A473F73D; Thu, 3 Jun 2021 07:07:01 -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 v7 3/3] sched/doc: Update the CPU capacity asymmetry bits Date: Thu, 3 Jun 2021 15:06:27 +0100 Message-Id: <20210603140627.8409-4-beata.michalska@arm.com> In-Reply-To: <20210603140627.8409-1-beata.michalska@arm.com> References: <20210603140627.8409-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 Reviewed-by: Dietmar Eggemann --- 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