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 kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9F95AC433F5 for ; Tue, 1 Feb 2022 10:17:08 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 310346B018B; Tue, 1 Feb 2022 05:17:08 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 2BFB46B018C; Tue, 1 Feb 2022 05:17:08 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 1608F8D0054; Tue, 1 Feb 2022 05:17:08 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0184.hostedemail.com [216.40.44.184]) by kanga.kvack.org (Postfix) with ESMTP id 036276B018B for ; Tue, 1 Feb 2022 05:17:08 -0500 (EST) Received: from smtpin10.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay01.hostedemail.com (Postfix) with ESMTP id B485D182030AD for ; Tue, 1 Feb 2022 10:17:07 +0000 (UTC) X-FDA: 79093808094.10.93E9EAA Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by imf26.hostedemail.com (Postfix) with ESMTP id 24DBC140007 for ; Tue, 1 Feb 2022 10:17:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1643710626; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=1rSMPibeU2/x9y1HGJmwIBX0MF6r0zdDZVn4ZSeYeqM=; b=BTJtMh/m9wI877MoJHJo8Ss1XH0a7PwVHOmxVkpkHjrxvMdSxPzz8ZscqYEXV3uEF4h7Nq JAbfc3pvCb0vO5IAiObiWenIWaQN7vCjMmb1ZSrYmeQUVRkIqULicGCQjO5sN+tCZd7zD+ 9kExqb8KeIhBd1T5B10BbJPp9h+gTdo= Received: from mail-wm1-f70.google.com (mail-wm1-f70.google.com [209.85.128.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-672-9jQ_sv3dOEuxRISvKK4LWQ-1; Tue, 01 Feb 2022 05:17:05 -0500 X-MC-Unique: 9jQ_sv3dOEuxRISvKK4LWQ-1 Received: by mail-wm1-f70.google.com with SMTP id r9-20020a1c4409000000b00352cf8b74dcso564609wma.0 for ; Tue, 01 Feb 2022 02:17:05 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:organization:in-reply-to :content-transfer-encoding; bh=1rSMPibeU2/x9y1HGJmwIBX0MF6r0zdDZVn4ZSeYeqM=; b=O4yZtuXiT2emQ3qgCcIRW0S5G9d2fD4ViIzancGGR/GJDQkr5OPBbTUu9LtvU7y6v0 VfiSxnIS2YbOWtC9Ns8PrptMAmfbgf10lkvWZPNPilF3bZfKi1H4/tM7S+oJaDWQ0T+0 /uwHgfRpV1YiAtF7j9SoBLsga6U1UpOytzm2nqZdz7Qcc9J446N9kHdSbsSUAVY6jpar o9KdL61BeqBpMPmQc8lEmOvAfrbYs+v4WO3jEJTU17Hl4chUdF4ilfFptRwUsSzrXw8c bVfBvJSZzqoEySN6ria7663HBkumplwKqyTaqicKq/V6U63BZ3QU789B237507wqrIzZ HydQ== X-Gm-Message-State: AOAM53298HiIeUx3a/0f/HbDjSK+34h6PZzVkfT/xVk+29Ezi0RbtzBw 8xTvCznfxVH9fLDfIesmXSMc7KYsiWa6+S01IxFgqileIGT3DWBM2lOpm2jovrmc5fszlkKRcAK A9whwn0cwz34= X-Received: by 2002:adf:f54d:: with SMTP id j13mr20271525wrp.596.1643710624126; Tue, 01 Feb 2022 02:17:04 -0800 (PST) X-Google-Smtp-Source: ABdhPJwW9cnbVOET7eNHaJPpg1tW+PwHgA1p1BZnH/wRYWshALkMr1QDZjc+KGZLPaL4fKlWIFXhpA== X-Received: by 2002:adf:f54d:: with SMTP id j13mr20271503wrp.596.1643710623856; Tue, 01 Feb 2022 02:17:03 -0800 (PST) Received: from ?IPV6:2003:cb:c711:ba00:67b6:a3ab:b0a8:9517? (p200300cbc711ba0067b6a3abb0a89517.dip0.t-ipconnect.de. [2003:cb:c711:ba00:67b6:a3ab:b0a8:9517]) by smtp.gmail.com with ESMTPSA id p2sm1600619wmc.33.2022.02.01.02.17.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 01 Feb 2022 02:17:03 -0800 (PST) Message-ID: <19907f0c-4d83-4d85-4233-f4ee727574a0@redhat.com> Date: Tue, 1 Feb 2022 11:17:01 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.4.0 Subject: Re: [PATCH RFC v1] drivers/base/node: consolidate node device subsystem initialization in node_dev_init() To: Oscar Salvador 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 References: <20220128151540.164759-1-david@redhat.com> <3be2e20c-f0b9-c080-adf4-b0e17c046eb0@redhat.com> <20220131094041.GA15392@linux> From: David Hildenbrand Organization: Red Hat In-Reply-To: <20220131094041.GA15392@linux> X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Rspam-User: nil X-Rspamd-Server: rspam05 X-Rspamd-Queue-Id: 24DBC140007 X-Stat-Signature: peqsma6ofoyk8j53cqggd95px6o5eihj Authentication-Results: imf26.hostedemail.com; dkim=pass header.d=redhat.com header.s=mimecast20190719 header.b="BTJtMh/m"; dmarc=pass (policy=none) header.from=redhat.com; spf=none (imf26.hostedemail.com: domain of david@redhat.com has no SPF policy when checking 170.10.133.124) smtp.mailfrom=david@redhat.com X-HE-Tag: 1643710626-252283 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On 31.01.22 10:40, Oscar Salvador wrote: > 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. I'll adjust the first paragraph to: ... and call node_dev_init() after memory_dev_init() from driver_init(), so before any of the existing arch/subsys calls. All online nodes should be known at that point: early during boot, arch code determines node and zone ranges and sets the relevant nodes online; usually this happens in setup_arch(). Thanks! -- Thanks, David / dhildenb