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 838E71099B41 for ; Fri, 20 Mar 2026 22:14:08 +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:Cc:To:In-Reply-To:References:Message-Id :MIME-Version:Subject:Date:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=9x+KBRrEStljuIdMwohT+quIckqT6oCYrfgJ1s81OJ0=; b=3DDKGWi9feGeEK ui1TbNIPl2b+R+e7sEwB0sNC4ivDpXJ90djRX3qfvoGd9fLKFgOsua4+y7VOy+yCtx7/HIAivaIfJ oWbRGCYbCNtVfk1zDTyzz4MTDK3NkxotAgmiDRmtHw0W0gqTtpUi3OFtq14ItsTS+yV4lDQPlusmj UKfwYYc25prg5mZ52IYlZ+yruVWzneSDfYVQcIX7S5+HwNC3RLn05JJUItDNdc+76WHSk3jOfabsD M1a3TRtQEQ7eDBzUjD9sTGd09tzbs+swfTsTkApp+9i5h10HvBytuhpugwewkSXuHa3NKVQ557B6j OXHEu8g6Q9e9nmOa7NKw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98.2 #2 (Red Hat Linux)) id 1w3i6U-0000000DfNm-1b1O; Fri, 20 Mar 2026 22:14:02 +0000 Received: from tor.source.kernel.org ([172.105.4.254]) by bombadil.infradead.org with esmtps (Exim 4.98.2 #2 (Red Hat Linux)) id 1w3i6T-0000000DfNR-2fmv for linux-riscv@lists.infradead.org; Fri, 20 Mar 2026 22:14:01 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by tor.source.kernel.org (Postfix) with ESMTP id 1777460142; Fri, 20 Mar 2026 22:14:01 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 22BC5C2BC87; Fri, 20 Mar 2026 22:13:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1774044840; bh=mvXhiGTn6tZZYnNOOoiRbg2GgcaMPiyLXwyjxmdxo84=; h=From:Date:Subject:References:In-Reply-To:To:Cc:From; b=X/uB2w7DSbxaqWWZI0SFouAEqRYt5ziW1QewNaYsFL+YJCSIra6vwkHxw1G9GGCh4 BIg7cd7GsHXYGOKUNs0MzTHjHG60jQ69wHz78GZiVzLl9CYVKK8mKlaJBjYPupxasS g+bH6a1n9UMg+IiOGJihFzUSK7KfYpQoRfoiR5xltvNtvoFnAacVxiUXKk85xWL8c9 muE+/XC1RcriPyCEgQuzM4jbHkE9K1Cv3yzKRDknP/UJEsuMIMFvejFsVGjnmVpp4O pbmnmWeUm1R8FQmqFTejFLSSs151sXs6nnngVkaakFF4+Yn2aN1kiPBhn3e/pwFWuy w+3VzFUlJqhAg== From: "David Hildenbrand (Arm)" Date: Fri, 20 Mar 2026 23:13:36 +0100 Subject: [PATCH v2 04/15] mm/Kconfig: make CONFIG_MEMORY_HOTPLUG depend on CONFIG_SPARSEMEM_VMEMMAP MIME-Version: 1.0 Message-Id: <20260320-sparsemem_cleanups-v2-4-096addc8800d@kernel.org> References: <20260320-sparsemem_cleanups-v2-0-096addc8800d@kernel.org> In-Reply-To: <20260320-sparsemem_cleanups-v2-0-096addc8800d@kernel.org> To: linux-kernel@vger.kernel.org Cc: Andrew Morton , Oscar Salvador , Axel Rasmussen , Yuanchu Xie , Wei Xu , Lorenzo Stoakes , "Liam R. Howlett" , Vlastimil Babka , Mike Rapoport , Suren Baghdasaryan , Michal Hocko , Sidhartha Kumar , linux-mm@kvack.org, linux-cxl@vger.kernel.org, linux-riscv@lists.infradead.org, "David Hildenbrand (Arm)" X-Mailer: b4 0.13.0 X-BeenThere: linux-riscv@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-riscv" Errors-To: linux-riscv-bounces+linux-riscv=archiver.kernel.org@lists.infradead.org Ever since commit f8f03eb5f0f9 ("mm: stop making SPARSEMEM_VMEMMAP user-selectable"), an architecture that supports CONFIG_SPARSEMEM_VMEMMAP (by selecting SPARSEMEM_VMEMMAP_ENABLE) can no longer enable CONFIG_SPARSEMEM without CONFIG_SPARSEMEM_VMEMMAP. Right now, CONFIG_MEMORY_HOTPLUG is guarded by CONFIG_SPARSEMEM. However, CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG is only enabled by * arm64: which selects SPARSEMEM_VMEMMAP_ENABLE * loongarch: which selects SPARSEMEM_VMEMMAP_ENABLE * powerpc (64bit): which selects SPARSEMEM_VMEMMAP_ENABLE * riscv (64bit): which selects SPARSEMEM_VMEMMAP_ENABLE * s390 with SPARSEMEM: which selects SPARSEMEM_VMEMMAP_ENABLE * x86 (64bit): which selects SPARSEMEM_VMEMMAP_ENABLE So, we can make CONFIG_MEMORY_HOTPLUG depend on CONFIG_SPARSEMEM_VMEMMAP without affecting any setups. Reviewed-by: Lorenzo Stoakes (Oracle) Reviewed-by: Mike Rapoport (Microsoft) Signed-off-by: David Hildenbrand (Arm) --- mm/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mm/Kconfig b/mm/Kconfig index ebd8ea353687..c012944938a7 100644 --- a/mm/Kconfig +++ b/mm/Kconfig @@ -472,7 +472,7 @@ config ARCH_ENABLE_MEMORY_HOTREMOVE menuconfig MEMORY_HOTPLUG bool "Memory hotplug" select MEMORY_ISOLATION - depends on SPARSEMEM + depends on SPARSEMEM_VMEMMAP depends on ARCH_ENABLE_MEMORY_HOTPLUG depends on 64BIT select NUMA_KEEP_MEMINFO if NUMA -- 2.43.0 _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv