From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mm01.cs.columbia.edu (mm01.cs.columbia.edu [128.59.11.253]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8CC0FECAAD1 for ; Thu, 1 Sep 2022 17:59:36 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mm01.cs.columbia.edu (Postfix) with ESMTP id F2DCB49F21; Thu, 1 Sep 2022 13:59:35 -0400 (EDT) X-Virus-Scanned: at lists.cs.columbia.edu Received: from mm01.cs.columbia.edu ([127.0.0.1]) by localhost (mm01.cs.columbia.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FkSjZ9aQ9r0d; Thu, 1 Sep 2022 13:59:34 -0400 (EDT) Received: from mm01.cs.columbia.edu (localhost [127.0.0.1]) by mm01.cs.columbia.edu (Postfix) with ESMTP id 09EE049F31; Thu, 1 Sep 2022 13:59:34 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mm01.cs.columbia.edu (Postfix) with ESMTP id B29ED49F31 for ; Thu, 1 Sep 2022 13:59:32 -0400 (EDT) X-Virus-Scanned: at lists.cs.columbia.edu Received: from mm01.cs.columbia.edu ([127.0.0.1]) by localhost (mm01.cs.columbia.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MgQymnrDqgzo for ; Thu, 1 Sep 2022 13:59:31 -0400 (EDT) Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by mm01.cs.columbia.edu (Postfix) with ESMTPS id 4B1E549F14 for ; Thu, 1 Sep 2022 13:59:31 -0400 (EDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 329A6611C0; Thu, 1 Sep 2022 17:59:30 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6ED34C433C1; Thu, 1 Sep 2022 17:59:27 +0000 (UTC) Date: Thu, 1 Sep 2022 18:59:23 +0100 From: Catalin Marinas To: kernel test robot Subject: Re: [PATCH v3 3/7] mm: Add PG_arch_3 page flag Message-ID: References: <20220810193033.1090251-4-pcc@google.com> <202208111500.62e0Bl2l-lkp@intel.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <202208111500.62e0Bl2l-lkp@intel.com> Cc: kbuild-all@lists.01.org, kvm@vger.kernel.org, Peter Collingbourne , Cornelia Huck , Steven Price , Evgenii Stepanov , Marc Zyngier , Vincenzo Frascino , Will Deacon , kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org X-BeenThere: kvmarm@lists.cs.columbia.edu X-Mailman-Version: 2.1.14 Precedence: list List-Id: Where KVM/ARM decisions are made List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kvmarm-bounces@lists.cs.columbia.edu Sender: kvmarm-bounces@lists.cs.columbia.edu On Thu, Aug 11, 2022 at 03:16:08PM +0800, kernel test robot wrote: > Thank you for the patch! Perhaps something to improve: > > [auto build test WARNING on arm64/for-next/core] > [also build test WARNING on linus/master next-20220811] > [cannot apply to kvmarm/next arm/for-next soc/for-next xilinx-xlnx/master v5.19] > [If your patch is applied to the wrong git tree, kindly drop us a note. > And when submitting patch, we suggest to use '--base' as documented in > https://git-scm.com/docs/git-format-patch#_base_tree_information] > > url: https://github.com/intel-lab-lkp/linux/commits/Peter-Collingbourne/KVM-arm64-permit-MAP_SHARED-mappings-with-MTE-enabled/20220811-033310 > base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core > config: loongarch-defconfig (https://download.01.org/0day-ci/archive/20220811/202208111500.62e0Bl2l-lkp@intel.com/config) > compiler: loongarch64-linux-gcc (GCC) 12.1.0 > reproduce (this is a W=1 build): > wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross > chmod +x ~/bin/make.cross > # https://github.com/intel-lab-lkp/linux/commit/1a400517d8428df0ec9f86f8d303b2227ee9702f > git remote add linux-review https://github.com/intel-lab-lkp/linux > git fetch --no-tags linux-review Peter-Collingbourne/KVM-arm64-permit-MAP_SHARED-mappings-with-MTE-enabled/20220811-033310 > git checkout 1a400517d8428df0ec9f86f8d303b2227ee9702f > # save the config file > mkdir build_dir && cp config build_dir/.config > COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=loongarch SHELL=/bin/bash > > If you fix the issue, kindly add following tag where applicable > Reported-by: kernel test robot > > All warnings (new ones prefixed by >>): > > >> mm/memory.c:92:2: warning: #warning Unfortunate NUMA and NUMA Balancing config, growing page-frame for last_cpupid. [-Wcpp] > 92 | #warning Unfortunate NUMA and NUMA Balancing config, growing page-frame for last_cpupid. > | ^~~~~~~ > > > vim +92 mm/memory.c > > 42b7772812d15b Jan Beulich 2008-07-23 90 > af27d9403f5b80 Arnd Bergmann 2018-02-16 91 #if defined(LAST_CPUPID_NOT_IN_PAGE_FLAGS) && !defined(CONFIG_COMPILE_TEST) > 90572890d20252 Peter Zijlstra 2013-10-07 @92 #warning Unfortunate NUMA and NUMA Balancing config, growing page-frame for last_cpupid. > 75980e97daccfc Peter Zijlstra 2013-02-22 93 #endif > 75980e97daccfc Peter Zijlstra 2013-02-22 94 It looks like ith CONFIG_NUMA_BALANCING=y on loongarch we run out of spare bits in page->flags to fit last_cpupid. The reason we don't see it on arm64 is that we select SPARSEMEM_VMEMMAP and SECTIONS_WIDTH becomes 0. On loongarch SECTIONS_WIDTH takes 19 bits (48 - 29) in page->flags. I think instead of always defining PG_arch_{2,3} if CONFIG_64BIT, we could add a CONFIG_ARCH_WANTS_PG_ARCH_23 option and only select it on arm64 for the time being. -- Catalin _______________________________________________ kvmarm mailing list kvmarm@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/kvmarm From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 14DC9ECAAD1 for ; Thu, 1 Sep 2022 18:00:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=QNDLe/5qwH18VeBlQh2TeTAwX6JNlpyvvXniv0E2QC0=; b=uvp7oMZNQBYss0 smgLb1M4RIW28yJlcxoNv52ucUAsvju22CNrIQ3nE/vMtwP8P0vrwow5Zn/8s96FPXLSNQO2SSFXD 2ZlHJzeJqypPNiCMxXQv2nI2bYaTLNwIsBJwgBEM2cuYo8OOyceVOaJ2mvs0/no3kuyd8ZicpMtCN /GS7TsF+B0rx9U9QSjH1p08vb36P6G8G0T0ubR3+YKoyyrWgTgAMEbKx9z6yHxFOq34lKaZnRVNK9 MfOj0R6HOIhzhVeS+/hUNbopVMQ5BQNDCb5KWCpLxkyb8LKx7J7fD0Y0puCNIyjH62oV8AqK1pIjm KMKgVEFVYg5L/4jAQc4A==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oToTW-00Dkxn-J8; Thu, 01 Sep 2022 17:59:34 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1oToTT-00DkwE-8l for linux-arm-kernel@lists.infradead.org; Thu, 01 Sep 2022 17:59:33 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 329A6611C0; Thu, 1 Sep 2022 17:59:30 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6ED34C433C1; Thu, 1 Sep 2022 17:59:27 +0000 (UTC) Date: Thu, 1 Sep 2022 18:59:23 +0100 From: Catalin Marinas To: kernel test robot Cc: Peter Collingbourne , linux-arm-kernel@lists.infradead.org, kvmarm@lists.cs.columbia.edu, kbuild-all@lists.01.org, Cornelia Huck , Will Deacon , Marc Zyngier , Evgenii Stepanov , kvm@vger.kernel.org, Steven Price , Vincenzo Frascino Subject: Re: [PATCH v3 3/7] mm: Add PG_arch_3 page flag Message-ID: References: <20220810193033.1090251-4-pcc@google.com> <202208111500.62e0Bl2l-lkp@intel.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <202208111500.62e0Bl2l-lkp@intel.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220901_105931_406509_1994A4E6 X-CRM114-Status: GOOD ( 20.36 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Aug 11, 2022 at 03:16:08PM +0800, kernel test robot wrote: > Thank you for the patch! Perhaps something to improve: > > [auto build test WARNING on arm64/for-next/core] > [also build test WARNING on linus/master next-20220811] > [cannot apply to kvmarm/next arm/for-next soc/for-next xilinx-xlnx/master v5.19] > [If your patch is applied to the wrong git tree, kindly drop us a note. > And when submitting patch, we suggest to use '--base' as documented in > https://git-scm.com/docs/git-format-patch#_base_tree_information] > > url: https://github.com/intel-lab-lkp/linux/commits/Peter-Collingbourne/KVM-arm64-permit-MAP_SHARED-mappings-with-MTE-enabled/20220811-033310 > base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core > config: loongarch-defconfig (https://download.01.org/0day-ci/archive/20220811/202208111500.62e0Bl2l-lkp@intel.com/config) > compiler: loongarch64-linux-gcc (GCC) 12.1.0 > reproduce (this is a W=1 build): > wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross > chmod +x ~/bin/make.cross > # https://github.com/intel-lab-lkp/linux/commit/1a400517d8428df0ec9f86f8d303b2227ee9702f > git remote add linux-review https://github.com/intel-lab-lkp/linux > git fetch --no-tags linux-review Peter-Collingbourne/KVM-arm64-permit-MAP_SHARED-mappings-with-MTE-enabled/20220811-033310 > git checkout 1a400517d8428df0ec9f86f8d303b2227ee9702f > # save the config file > mkdir build_dir && cp config build_dir/.config > COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=loongarch SHELL=/bin/bash > > If you fix the issue, kindly add following tag where applicable > Reported-by: kernel test robot > > All warnings (new ones prefixed by >>): > > >> mm/memory.c:92:2: warning: #warning Unfortunate NUMA and NUMA Balancing config, growing page-frame for last_cpupid. [-Wcpp] > 92 | #warning Unfortunate NUMA and NUMA Balancing config, growing page-frame for last_cpupid. > | ^~~~~~~ > > > vim +92 mm/memory.c > > 42b7772812d15b Jan Beulich 2008-07-23 90 > af27d9403f5b80 Arnd Bergmann 2018-02-16 91 #if defined(LAST_CPUPID_NOT_IN_PAGE_FLAGS) && !defined(CONFIG_COMPILE_TEST) > 90572890d20252 Peter Zijlstra 2013-10-07 @92 #warning Unfortunate NUMA and NUMA Balancing config, growing page-frame for last_cpupid. > 75980e97daccfc Peter Zijlstra 2013-02-22 93 #endif > 75980e97daccfc Peter Zijlstra 2013-02-22 94 It looks like ith CONFIG_NUMA_BALANCING=y on loongarch we run out of spare bits in page->flags to fit last_cpupid. The reason we don't see it on arm64 is that we select SPARSEMEM_VMEMMAP and SECTIONS_WIDTH becomes 0. On loongarch SECTIONS_WIDTH takes 19 bits (48 - 29) in page->flags. I think instead of always defining PG_arch_{2,3} if CONFIG_64BIT, we could add a CONFIG_ARCH_WANTS_PG_ARCH_23 option and only select it on arm64 for the time being. -- Catalin _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 39F3FECAAD1 for ; Thu, 1 Sep 2022 17:59:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234005AbiIAR7i (ORCPT ); Thu, 1 Sep 2022 13:59:38 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40072 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233908AbiIAR7e (ORCPT ); Thu, 1 Sep 2022 13:59:34 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 69569786FD for ; Thu, 1 Sep 2022 10:59:32 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id D0AF9B8259D for ; Thu, 1 Sep 2022 17:59:30 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6ED34C433C1; Thu, 1 Sep 2022 17:59:27 +0000 (UTC) Date: Thu, 1 Sep 2022 18:59:23 +0100 From: Catalin Marinas To: kernel test robot Cc: Peter Collingbourne , linux-arm-kernel@lists.infradead.org, kvmarm@lists.cs.columbia.edu, kbuild-all@lists.01.org, Cornelia Huck , Will Deacon , Marc Zyngier , Evgenii Stepanov , kvm@vger.kernel.org, Steven Price , Vincenzo Frascino Subject: Re: [PATCH v3 3/7] mm: Add PG_arch_3 page flag Message-ID: References: <20220810193033.1090251-4-pcc@google.com> <202208111500.62e0Bl2l-lkp@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <202208111500.62e0Bl2l-lkp@intel.com> Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On Thu, Aug 11, 2022 at 03:16:08PM +0800, kernel test robot wrote: > Thank you for the patch! Perhaps something to improve: > > [auto build test WARNING on arm64/for-next/core] > [also build test WARNING on linus/master next-20220811] > [cannot apply to kvmarm/next arm/for-next soc/for-next xilinx-xlnx/master v5.19] > [If your patch is applied to the wrong git tree, kindly drop us a note. > And when submitting patch, we suggest to use '--base' as documented in > https://git-scm.com/docs/git-format-patch#_base_tree_information] > > url: https://github.com/intel-lab-lkp/linux/commits/Peter-Collingbourne/KVM-arm64-permit-MAP_SHARED-mappings-with-MTE-enabled/20220811-033310 > base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core > config: loongarch-defconfig (https://download.01.org/0day-ci/archive/20220811/202208111500.62e0Bl2l-lkp@intel.com/config) > compiler: loongarch64-linux-gcc (GCC) 12.1.0 > reproduce (this is a W=1 build): > wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross > chmod +x ~/bin/make.cross > # https://github.com/intel-lab-lkp/linux/commit/1a400517d8428df0ec9f86f8d303b2227ee9702f > git remote add linux-review https://github.com/intel-lab-lkp/linux > git fetch --no-tags linux-review Peter-Collingbourne/KVM-arm64-permit-MAP_SHARED-mappings-with-MTE-enabled/20220811-033310 > git checkout 1a400517d8428df0ec9f86f8d303b2227ee9702f > # save the config file > mkdir build_dir && cp config build_dir/.config > COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=loongarch SHELL=/bin/bash > > If you fix the issue, kindly add following tag where applicable > Reported-by: kernel test robot > > All warnings (new ones prefixed by >>): > > >> mm/memory.c:92:2: warning: #warning Unfortunate NUMA and NUMA Balancing config, growing page-frame for last_cpupid. [-Wcpp] > 92 | #warning Unfortunate NUMA and NUMA Balancing config, growing page-frame for last_cpupid. > | ^~~~~~~ > > > vim +92 mm/memory.c > > 42b7772812d15b Jan Beulich 2008-07-23 90 > af27d9403f5b80 Arnd Bergmann 2018-02-16 91 #if defined(LAST_CPUPID_NOT_IN_PAGE_FLAGS) && !defined(CONFIG_COMPILE_TEST) > 90572890d20252 Peter Zijlstra 2013-10-07 @92 #warning Unfortunate NUMA and NUMA Balancing config, growing page-frame for last_cpupid. > 75980e97daccfc Peter Zijlstra 2013-02-22 93 #endif > 75980e97daccfc Peter Zijlstra 2013-02-22 94 It looks like ith CONFIG_NUMA_BALANCING=y on loongarch we run out of spare bits in page->flags to fit last_cpupid. The reason we don't see it on arm64 is that we select SPARSEMEM_VMEMMAP and SECTIONS_WIDTH becomes 0. On loongarch SECTIONS_WIDTH takes 19 bits (48 - 29) in page->flags. I think instead of always defining PG_arch_{2,3} if CONFIG_64BIT, we could add a CONFIG_ARCH_WANTS_PG_ARCH_23 option and only select it on arm64 for the time being. -- Catalin From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============5152913649566660361==" MIME-Version: 1.0 From: Catalin Marinas To: kbuild-all@lists.01.org Subject: Re: [PATCH v3 3/7] mm: Add PG_arch_3 page flag Date: Thu, 01 Sep 2022 18:59:23 +0100 Message-ID: In-Reply-To: <202208111500.62e0Bl2l-lkp@intel.com> List-Id: --===============5152913649566660361== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Thu, Aug 11, 2022 at 03:16:08PM +0800, kernel test robot wrote: > Thank you for the patch! Perhaps something to improve: > = > [auto build test WARNING on arm64/for-next/core] > [also build test WARNING on linus/master next-20220811] > [cannot apply to kvmarm/next arm/for-next soc/for-next xilinx-xlnx/master= v5.19] > [If your patch is applied to the wrong git tree, kindly drop us a note. > And when submitting patch, we suggest to use '--base' as documented in > https://git-scm.com/docs/git-format-patch#_base_tree_information] > = > url: https://github.com/intel-lab-lkp/linux/commits/Peter-Collingbourn= e/KVM-arm64-permit-MAP_SHARED-mappings-with-MTE-enabled/20220811-033310 > base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git f= or-next/core > config: loongarch-defconfig (https://download.01.org/0day-ci/archive/2022= 0811/202208111500.62e0Bl2l-lkp(a)intel.com/config) > compiler: loongarch64-linux-gcc (GCC) 12.1.0 > reproduce (this is a W=3D1 build): > wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbi= n/make.cross -O ~/bin/make.cross > chmod +x ~/bin/make.cross > # https://github.com/intel-lab-lkp/linux/commit/1a400517d8428df0e= c9f86f8d303b2227ee9702f > git remote add linux-review https://github.com/intel-lab-lkp/linux > git fetch --no-tags linux-review Peter-Collingbourne/KVM-arm64-pe= rmit-MAP_SHARED-mappings-with-MTE-enabled/20220811-033310 > git checkout 1a400517d8428df0ec9f86f8d303b2227ee9702f > # save the config file > mkdir build_dir && cp config build_dir/.config > COMPILER_INSTALL_PATH=3D$HOME/0day COMPILER=3Dgcc-12.1.0 make.cro= ss W=3D1 O=3Dbuild_dir ARCH=3Dloongarch SHELL=3D/bin/bash > = > If you fix the issue, kindly add following tag where applicable > Reported-by: kernel test robot > = > All warnings (new ones prefixed by >>): > = > >> mm/memory.c:92:2: warning: #warning Unfortunate NUMA and NUMA Balancin= g config, growing page-frame for last_cpupid. [-Wcpp] > 92 | #warning Unfortunate NUMA and NUMA Balancing config, growing p= age-frame for last_cpupid. > | ^~~~~~~ > = > = > vim +92 mm/memory.c > = > 42b7772812d15b Jan Beulich 2008-07-23 90 = > af27d9403f5b80 Arnd Bergmann 2018-02-16 91 #if defined(LAST_CPUPID_NOT= _IN_PAGE_FLAGS) && !defined(CONFIG_COMPILE_TEST) > 90572890d20252 Peter Zijlstra 2013-10-07 @92 #warning Unfortunate NUMA a= nd NUMA Balancing config, growing page-frame for last_cpupid. > 75980e97daccfc Peter Zijlstra 2013-02-22 93 #endif > 75980e97daccfc Peter Zijlstra 2013-02-22 94 = It looks like ith CONFIG_NUMA_BALANCING=3Dy on loongarch we run out of spare bits in page->flags to fit last_cpupid. The reason we don't see it on arm64 is that we select SPARSEMEM_VMEMMAP and SECTIONS_WIDTH becomes 0. On loongarch SECTIONS_WIDTH takes 19 bits (48 - 29) in page->flags. I think instead of always defining PG_arch_{2,3} if CONFIG_64BIT, we could add a CONFIG_ARCH_WANTS_PG_ARCH_23 option and only select it on arm64 for the time being. -- = Catalin --===============5152913649566660361==--