Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp659176pxb; Tue, 1 Feb 2022 07:53:43 -0800 (PST) X-Google-Smtp-Source: ABdhPJwtv7Sd5OS8EBGYGPFmhhPk/7IsXMkuvxi7OGWliMrZ45ZcdMSZgn++dWPWa3q1puUq+Dfu X-Received: by 2002:a17:90b:4ad0:: with SMTP id mh16mr2985653pjb.89.1643730822856; Tue, 01 Feb 2022 07:53:42 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643730822; cv=none; d=google.com; s=arc-20160816; b=O8iJkwF7jKh2SnhLELsASvDzWMTYCaBApjJWfDxU7em+nKNRhzdV9kGWB+bIIA+AUk JKzCDRNy6DcHRM/0aMwIig5+GO6at0L532lXD2jpSOepTIquyfq7unn14H1TO3PYCIhS +QheOB7t1gNd4uGmkqh4sW9uuPAXTiv1ner3qei3NjsuNRrNHPaf3PXknSmrKrbHk629 czjzVm09QRcep7WaEXPqLCrkU/pMAtvjWhSYUhmwkVCJ+TCOGgPk9DggVznCAr76fdHZ wBFZhMwie0AOq6hbhw8Y+VJblghQppQSVDVcHmG618pa72Hh3aH3CQA3wdCTGUKP/cf3 a6Iw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature:dkim-signature; bh=Y00ZKxq/dpqUDwh0rX8TbLgQbvVTvbkuCSKi0GTnT4o=; b=OhE/tMwEm4LoXEOm0v9jcv8uc5L8zrFweY3NdsoRRayH3/mFxEEVgE0mZGcQSis+ZY dU65UGBhJ5E0fxtKdVuFGY/065Ev4bmHyjZ2KvMiZ2OdbJq4NqGDjp8i76U395NiGgGg B+OwIvjNcYAommSZQf7wcL6R41pvRuJ7LLyNeEaq7doNRqwiWrI23I77+7bnLbrhYo/k V2d3P+IV9VP2mMhj+rhfab3F4lGzCco+eesDAschBu68SP6JkpEBkv0jOvKjKkDijHa/ Dgk+XnzOcXYdpkLKRW+27BQP1nXIHo9XAdsqOWj1u6UkEzUkIz5oQn08Imki/LlNCmU4 49tQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.de header.s=susede2_rsa header.b=TAvjGCxB; dkim=neutral (no key) header.i=@suse.de; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=suse.de Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id x37si16942736pgl.334.2022.02.01.07.53.31; Tue, 01 Feb 2022 07:53:42 -0800 (PST) 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; dkim=pass header.i=@suse.de header.s=susede2_rsa header.b=TAvjGCxB; dkim=neutral (no key) header.i=@suse.de; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=suse.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240902AbiAaJkw (ORCPT + 99 others); Mon, 31 Jan 2022 04:40:52 -0500 Received: from smtp-out2.suse.de ([195.135.220.29]:37060 "EHLO smtp-out2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238819AbiAaJkt (ORCPT ); Mon, 31 Jan 2022 04:40:49 -0500 Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id 42D361F380; Mon, 31 Jan 2022 09:40:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1643622047; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Y00ZKxq/dpqUDwh0rX8TbLgQbvVTvbkuCSKi0GTnT4o=; b=TAvjGCxBgtVEooteuwYwy7uWXHIEi1iRNO342s4/jJ+IIGBmHSjZzV5GBJojCxowtd9VF/ o3CAUfL8yGH9rRehhR4/C5FstjONcFAU8j7o3FYVmx80A08KFhFcu/K4azbvNlmWYom+Ua 6mK0Ha0OUepOw9iyGtTEgdVyGEbI2ng= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1643622047; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Y00ZKxq/dpqUDwh0rX8TbLgQbvVTvbkuCSKi0GTnT4o=; b=xUgFlc+6YdMvHQgFdTVnfhl595dV1vnsZnMruHRjkkwO5586I6U3elglHK3ZC5shbyTZxG 3d8GjzSobgWcibCQ== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 7204D13B68; Mon, 31 Jan 2022 09:40:45 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id f0PrF52u92G+DgAAMHmgww (envelope-from ); Mon, 31 Jan 2022 09:40:45 +0000 Date: Mon, 31 Jan 2022 10:40:43 +0100 From: Oscar Salvador To: David Hildenbrand Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, Andrew Morton , Greg Kroah-Hartman , Michal Hocko , Catalin Marinas , Will Deacon , Thomas Bogendoerfer , Michael Ellerman , Benjamin Herrenschmidt , Paul Mackerras , Paul Walmsley , Palmer Dabbelt , Albert Ou , Heiko Carstens , Vasily Gorbik , Yoshinori Sato , Rich Felker , "David S. Miller" , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , "Rafael J. Wysocki" , x86@kernel.org, linux-arm-kernel@lists.infradead.org, linux-ia64@vger.kernel.org, linux-mips@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-riscv@lists.infradead.org, linux-s390@vger.kernel.org, linux-sh@vger.kernel.org, sparclinux@vger.kernel.org Subject: Re: [PATCH RFC v1] drivers/base/node: consolidate node device subsystem initialization in node_dev_init() Message-ID: <20220131094041.GA15392@linux> References: <20220128151540.164759-1-david@redhat.com> <3be2e20c-f0b9-c080-adf4-b0e17c046eb0@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3be2e20c-f0b9-c080-adf4-b0e17c046eb0@redhat.com> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 31, 2022 at 08:48:54AM +0100, David Hildenbrand wrote: > Hi Oscar, Hi David :-), > Right, and the idea is that the online state of nodes (+ node/zone > ranges) already has to be known at that point in time, because > otherwise, we'd be in bigger trouble. Yeah, I wanted to check where exactly did we mark the nodes online, and for the few architectures I checked it happens in setup_arch(), which is called very early in start_kernel(), while driver_init() gets called through arch_call_rest_init(), which happens at the end of the function. I am not sure whether we want to remark that somehow in the changelog, so it is crystal clear that by the time the node_dev_init() gets called, we already set the nodes online. Anyway, just saying, but is fine as is. -- Oscar Salvador SUSE Labs