Received: by 2002:a05:6a10:a0d1:0:0:0:0 with SMTP id j17csp1174342pxa; Thu, 6 Aug 2020 01:10:18 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwq6ThPKM/6OjqgV+7gOOs7OMHa/WMHrMSXRVQooIg+CwuXfs3OSJpzHuIQZrgab0CtnAgO X-Received: by 2002:a17:906:1453:: with SMTP id q19mr3275338ejc.111.1596701418095; Thu, 06 Aug 2020 01:10:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1596701418; cv=none; d=google.com; s=arc-20160816; b=NUH5W3T75uP5ZYfY48DZiKXLWacemkl3WpAcmzu/NcdYnkbSaIOmOX4XTr3RCrRMIN zYppSrj/46y2BObgeD3II7RIgbURwPhfV+bLoCThV9ki9AYuWx3DTxR26IEMfjeYhAdH HmA4GMm7fgZQANGMDcCnHnQT5kL8b7vlrrR0SpBK/q1Y6y0ZOAmVJnX5KaITstnyKy56 hKYc6MTIKMiWfmhyCWl3Kpl4uI8+qrLn0A8f1nKCOk1bG43wMdPqGMr9NTYBB0AmT9ly weFMfTle2IgoHBZErbOoUTHD53MBOSRM1jivnqwhcdCzNm6Qh70DlEV7zFSaO92Xs383 ibqQ== 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=CChxpttX1lOn7gXG1WBfEQJaAwy1VXYoedI12xqGQB4=; b=mx9kCDNFAUTbvcyu3dNM7bGAlluJymwm5IlnozWEw/1f20pCZoUzNWOVy9YFGaXdlT 1/Y0i0QS/+ONAAFwjmVcxSfA/8O8wn2wow/VPq6OA3AqSQoReToQeSXMphi0WFsG0x9g 2/F6/OVm6AJifBtcnDX4st+0tSgpIXyuejAZ2BaZMcCTQAz0Kdve2G4pjVeUvw8rppQI f56g6KTHYWUf9l3wK8argGIlWLvq2jo6i1ExZ+l/v0yl8VOjoWtvot5XG/t+ORLFIhCo E0mm6VkBfsOATDfT2DpV+WkaN+cn7P/ga5C4/O6yVtdbAH1vIaLP2Kb8tmkv+aUoKwxN uzPA== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id h13si2877029ejl.221.2020.08.06.01.09.55; Thu, 06 Aug 2020 01:10:18 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728877AbgHFIIS (ORCPT + 99 others); Thu, 6 Aug 2020 04:08:18 -0400 Received: from elvis.franken.de ([193.175.24.41]:36293 "EHLO elvis.franken.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726799AbgHFIEO (ORCPT ); Thu, 6 Aug 2020 04:04:14 -0400 Received: from uucp (helo=alpha) by elvis.franken.de with local-bsmtp (Exim 3.36 #1) id 1k3arg-0000uJ-00; Thu, 06 Aug 2020 10:03:04 +0200 Received: by alpha.franken.de (Postfix, from userid 1000) id 42BD9C0C56; Thu, 6 Aug 2020 09:41:41 +0200 (CEST) Date: Thu, 6 Aug 2020 09:41:41 +0200 From: Thomas Bogendoerfer To: Mike Rapoport Cc: Paul Burton , Joshua Kinard , Jiaxun Yang , linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org, Mike Rapoport , kernel test robot , stable@vger.kernel.org Subject: Re: [PATCH] MIPS: SGI-IP27: always enable NUMA in Kconfig Message-ID: <20200806074141.GA5148@alpha.franken.de> References: <20200805125141.24987-1-rppt@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200805125141.24987-1-rppt@kernel.org> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Aug 05, 2020 at 03:51:41PM +0300, Mike Rapoport wrote: > From: Mike Rapoport > > When a configuration has NUMA disabled and SGI_IP27 enabled, the build > fails: > > CC kernel/bounds.s > CC arch/mips/kernel/asm-offsets.s > In file included from arch/mips/include/asm/topology.h:11, > from include/linux/topology.h:36, > from include/linux/gfp.h:9, > from include/linux/slab.h:15, > from include/linux/crypto.h:19, > from include/crypto/hash.h:11, > from include/linux/uio.h:10, > from include/linux/socket.h:8, > from include/linux/compat.h:15, > from arch/mips/kernel/asm-offsets.c:12: > include/linux/topology.h: In function 'numa_node_id': > arch/mips/include/asm/mach-ip27/topology.h:16:27: error: implicit declaration of function 'cputonasid'; did you mean 'cpu_vpe_id'? [-Werror=implicit-function-declaration] > #define cpu_to_node(cpu) (cputonasid(cpu)) > ^~~~~~~~~~ > include/linux/topology.h:119:9: note: in expansion of macro 'cpu_to_node' > return cpu_to_node(raw_smp_processor_id()); > ^~~~~~~~~~~ > include/linux/topology.h: In function 'cpu_cpu_mask': > arch/mips/include/asm/mach-ip27/topology.h:19:7: error: implicit declaration of function 'hub_data' [-Werror=implicit-function-declaration] > &hub_data(node)->h_cpus) > ^~~~~~~~ > include/linux/topology.h:210:9: note: in expansion of macro 'cpumask_of_node' > return cpumask_of_node(cpu_to_node(cpu)); > ^~~~~~~~~~~~~~~ > arch/mips/include/asm/mach-ip27/topology.h:19:21: error: invalid type argument of '->' (have 'int') > &hub_data(node)->h_cpus) > ^~ > include/linux/topology.h:210:9: note: in expansion of macro 'cpumask_of_node' > return cpumask_of_node(cpu_to_node(cpu)); > ^~~~~~~~~~~~~~~ > > Before switch from discontigmem to sparsemem, there always was > CONFIG_NEED_MULTIPLE_NODES=y because it was selected by DISCONTIGMEM. > Without DISCONTIGMEM it is possible to have SPARSEMEM without NUMA for > SGI_IP27 and as many things there rely on custom node definition, the > build breaks. > > As Thomas noted "... there are right now too many places in IP27 code, > which assumes NUMA enabled", the simplest solution would be to always > enable NUMA for SGI-IP27 builds. > > Reported-by: kernel test robot > Fixes: 397dc00e249e ("mips: sgi-ip27: switch from DISCONTIGMEM to SPARSEMEM") > Cc: stable@vger.kernel.org > Signed-off-by: Mike Rapoport > --- > arch/mips/Kconfig | 1 + > 1 file changed, 1 insertion(+) applied to mips-next. Thomas. -- Crap can work. Given enough thrust pigs will fly, but it's not necessarily a good idea. [ RFC1925, 2.3 ]