From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 1DC293812DD for ; Mon, 25 May 2026 17:12:00 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779729122; cv=none; b=Af1p20CrCScMIQfL8gm4S58LBYvzfXI8FCOcTX5DWpB9ddW4SAmu0jkk1J761Uqq0/JimRURa4vKgZQn2IFaVkmlHU5cyWW1uKhHRnkqJ8D07Qj0wW4VX7sQIJ5mXDBLWu7g536v37pw/S7NBrPK49ZlPB4NgcDhif8a10MXD9A= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779729122; c=relaxed/simple; bh=XayaibrGPIHBk53Jqde8bM6nvgu1J2VI+Qwy0hJOiGk=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=TkoLVPwuIsr2wvj0sKkw9sTYT5SFMWVt5LB8hM7wv10OT35ldXo+RGtRSb4Vihoe6A/U5sbjNWFegIx4CFrG1iwEM8w1XamCAWnD2xetIy6A0YEvv0SkAMnQQqt7bgNoZq+Il306Z8RVDxbtva6FfZMdeRB+vHtSGIj4lZOYnVU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=c0GkC8JB; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="c0GkC8JB" Received: by smtp.kernel.org (Postfix) with ESMTPSA id AD1941F000E9; Mon, 25 May 2026 17:11:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1779729120; bh=lppuGztfV3VAd9Pwvb8KD32Y3Ykhpo6lzmvPRGEXMHo=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=c0GkC8JBi6s+kPHIrR7x5eWxzlrBWPbVN7JRD3kvVG0gzNUV7Ut9TkT0Vs51PyYTK wOXSbJ8Rs2W1si5bDo37166aK3LgCK2zLuyOB48h2NzF4pPSfV0L6++kYqQTiGDfMi 9iU/inQrR+aoScNEW/B8QYe5oyPB8FdJtp1abpsDjMe3Sug4cUQRHJpKWIGFrZHOZQ bNNctxCvB049dg4NCUGmds1f23o4Q5gdmQl2EAmTeeOsGpMEYcZammGoDUSdKQzZZL hiE7o3quPtwsL8DwdU0NekrjkJTKao3aEhAtCQvNiye0I3BdsrP665kw7Aw8t2ZsHW seF0mOUytk/QQ== Date: Mon, 25 May 2026 19:11:52 +0200 From: "Oscar Salvador (SUSE)" To: Muchun Song Cc: Andrew Morton , David Hildenbrand , Muchun Song , Oscar Salvador , Michael Ellerman , Madhavan Srinivasan , Lorenzo Stoakes , "Liam R . Howlett" , Vlastimil Babka , Mike Rapoport , Suren Baghdasaryan , Michal Hocko , Nicholas Piggin , Christophe Leroy , Ackerley Tng , Frank van der Linden , aneesh.kumar@linux.ibm.com, joao.m.martins@oracle.com, linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 11/69] mm/sparse: Move sparse_vmemmap_init_nid_late() into sparse_init_nid() Message-ID: References: <20260513130542.35604-1-songmuchun@bytedance.com> <20260513130542.35604-12-songmuchun@bytedance.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260513130542.35604-12-songmuchun@bytedance.com> On Wed, May 13, 2026 at 09:04:39PM +0800, Muchun Song wrote: > sparse_vmemmap_init_nid_late() is still called separately from > mm_core_init_early(), away from the rest of the sparse initialization > path. > > Now that sparse_init() runs after zone initialization, call > sparse_vmemmap_init_nid_late() from sparse_init_nid() instead. This > keeps both sparse_vmemmap_init_nid_early() and > sparse_vmemmap_init_nid_late() in the sparse setup path. > > Signed-off-by: Muchun Song > Reviewed-by: Mike Rapoport (Microsoft) Reviewed-by: Oscar Salvador (SUSE) -- Oscar Salvador SUSE Labs