Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp1956260ybl; Thu, 9 Jan 2020 04:35:37 -0800 (PST) X-Google-Smtp-Source: APXvYqzNH8FUd513Jpo7o53O58kWyFVBbfRlrLRsu3oIn4xACk2z5zwDsswnkXwmOOMw0uV8NVwb X-Received: by 2002:a9d:75da:: with SMTP id c26mr8348634otl.40.1578573337150; Thu, 09 Jan 2020 04:35:37 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1578573337; cv=none; d=google.com; s=arc-20160816; b=B5J36LaQ5CiH8z4YM7ePlLy91vX1Kg0+TXjJ4wo3d5GmKla9nGKDPmXW2aGlup1pV7 788N+hp1PucKOU2ltm6mm6QSf1Jm4lxhj9w5dTX97WaR44Wyoy9k88mtMOUUsB4Ha3ng 3Mu2BSLTUtD7BNdeNTakvpvrpwCJBbkOkkIxwQdCPA5PTPE9N7mXnB7BN00v/rHF0zUT P6uE4nOmCNTQBsx1JkbdWROU88vkOnWmuuqUdiO6kOjW+H2bDGdtuvOYyCcSNU4DxngE pl3Hxr3/MSg/SKt76otcqfF/CKZKGCXX2FHb09tC2LCN/lZgaBjwonD9U3g3hzcpzv68 VTsw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=n01KiB6dQvLEZHpprMqd6L83Tt75aB9Ea4abjEV/EGo=; b=w/eYoo/PMPMKFwHFEM6FaeHJbroNsixz2LQ3ySb9a7nEoMdjm57jMHB5JIZNVpjc6N 6XqY6l2J+uthxZMzri3a7XQxZyjiPgPEmwlJR0+qIquQyQGQiN9YIAQQ/QnaRF7gDEsR douB/KonAIrJN9mDU23kAy7ePe+sLr20+CuceCrb79zeWXoBNvAarY2lgKOYJwJA5VKX 3VcyqVtXYJX5pfjCfI8eoes603E9giYKqlAgtDBtKjhyAYu46DX1NPrJqKOFQdD0AAUJ bZND6OV50hNvZzLCIqn4/l5xY1S9Za7o9uK8onI8EQlj/3XZAZNVKo/wsmC01WF7Eq4V 6whQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o128si3442961oih.66.2020.01.09.04.35.25; Thu, 09 Jan 2020 04:35:37 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729591AbgAIKwd (ORCPT + 99 others); Thu, 9 Jan 2020 05:52:33 -0500 Received: from foss.arm.com ([217.140.110.172]:56962 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729287AbgAIKwc (ORCPT ); Thu, 9 Jan 2020 05:52:32 -0500 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 E3F8831B; Thu, 9 Jan 2020 02:52:31 -0800 (PST) Received: from e105550-lin.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.121.207.14]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id E472C3F703; Thu, 9 Jan 2020 02:52:30 -0800 (PST) Date: Thu, 9 Jan 2020 10:52:28 +0000 From: Morten Rasmussen To: Valentin Schneider Cc: "Zengtao (B)" , Sudeep Holla , Linuxarm , Greg Kroah-Hartman , "Rafael J. Wysocki" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH] cpu-topology: warn if NUMA configurations conflicts with lower layer Message-ID: <20200109105228.GB10914@e105550-lin.cambridge.arm.com> References: <1577088979-8545-1-git-send-email-prime.zeng@hisilicon.com> <20191231164051.GA4864@bogus> <678F3D1BB717D949B966B68EAEB446ED340AE1D3@dggemm526-mbx.china.huawei.com> <20200102112955.GC4864@bogus> <678F3D1BB717D949B966B68EAEB446ED340AEB67@dggemm526-mbx.china.huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jan 02, 2020 at 01:22:19PM +0000, Valentin Schneider wrote: > On 02/01/2020 12:47, Zengtao (B) wrote: > >> > >> As I said, wrong configurations need to be detected when generating > >> DT/ACPI if possible. The above will print warning on systems with NUMA > >> within package. > >> > >> NUMA: 0-7, 8-15 > >> core_siblings: 0-15 > >> > >> The above is the example where the die has 16 CPUs and 2 NUMA nodes > >> within a package, your change throws error to the above config which is > >> wrong. > >> > > From your example, the core 7 and core 8 has got different LLC but the same Low > > Level cache? > > AFAIA what matters here is memory controllers, less so LLCs. Cores within > a single die could have private LLCs and separate memory controllers, or > shared LLC and separate memory controllers. Don't confuse cache boundaries, packages and nodes :-) core_siblings are cpus in the same package and doesn't say anything about cache boundaries. It is not given that there is sched_domain that matches the core_sibling span. The MC sched_domain is supposed to match the LLC span which might different for core_siblings. So the about example should be valid for a NUMA-in-package system with one package containing two nodes. Morten