Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp2735585pxj; Mon, 10 May 2021 09:33:41 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxQUr1BUAvpTkATTc4Ya0sb2yvxVDS2ojcnG9V7K6qPZjel1v5+w7lWpH8sBDouRJmHDdpv X-Received: by 2002:a02:ca0d:: with SMTP id i13mr22132782jak.98.1620664421252; Mon, 10 May 2021 09:33:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620664421; cv=none; d=google.com; s=arc-20160816; b=eLytrDZQzWmU+L9GO5UShVa6RUczE4p+hcRmwasw7tFy+x5/JsPfODFdv47rGWLKTG Z/LRHDAtER5YJYosLnMJobbmvEzHFf1AHlWS/7svui/KEUeUkmk774KItehoNAe2jVvX kSFMhQBZJdvA0bs6knFulaxE4YLsZGO65Trk+qJlpheaSi8FYrGWUSmaU0zSP+WEtvxn 95jVkmTqNgza3D6n85bI0gyHXbfIVWmliE+qhwXjesTuS50eviVd8DBt1bnNZRbLmGxH 0/OUO//57HvMuu3DR1EGDvw9I2UhxdRlsqhpEusNKEnF4nYKPZgHGLaxdNnU/HvXvzIs ycTg== 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=NPfSr2QLPLvjcXCL/ruC/BaAcqx8q1aD/fISoJLKXlcq8aLaltmgcngmBsXZtPnSae vEoNBNsLLvtGwQ9pwWAbVuEU//Fr9wE7Vq68gZnCfdca1VqsqT26WdbbwBRZEcbh/hbC 9MFl3GXoQ2WH7SjYiRAc9FS9Cu2f4FUcz0CIOeKdzyrdTOnzhXfvdROtszTYoSo0uPMF aavqaaT4IVvSqMIK9rHOKPNlxab22KXFsn/sd/Nv8LYisEumXc+HpCLnYVkq6h7Hds5O /DQuW8QPL8oHbSz7rdF4x7ujPiN12ns7zZCm6ZvwIqFeNjanAZDwr3cuJo15oAva+F8o K7KQ== 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 u10si16585424iln.13.2021.05.10.09.33.28; Mon, 10 May 2021 09:33:41 -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 S231388AbhEJQcz (ORCPT + 99 others); Mon, 10 May 2021 12:32:55 -0400 Received: from foss.arm.com ([217.140.110.172]:34020 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231626AbhEJQcf (ORCPT ); Mon, 10 May 2021 12:32:35 -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 2197B169C; Mon, 10 May 2021 09:31:30 -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 C3EAC3F73B; Mon, 10 May 2021 09:31:28 -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 v3 3/3] sched/doc: Update the CPU capacity asymmetry bits Date: Mon, 10 May 2021 17:30:58 +0100 Message-Id: <1620664258-11045-4-git-send-email-beata.michalska@arm.com> In-Reply-To: <1620664258-11045-1-git-send-email-beata.michalska@arm.com> References: <1620664258-11045-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