Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp415267ybt; Wed, 8 Jul 2020 03:05:55 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzSytPWZsAbnDebMobg7IlxrsHeft1HWVB4nYbiy3gVFGEzR4GQTnV7IXOPYzzuz4nUKIcG X-Received: by 2002:a50:d6dd:: with SMTP id l29mr66598439edj.345.1594202754812; Wed, 08 Jul 2020 03:05:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1594202754; cv=none; d=google.com; s=arc-20160816; b=pU+EjGeX2RdIomUOLY09Nfoxu7RZ+hmvd4Brbd+KZseQ6W80wI8p09FrUcCTv9UWNJ Ceo9zcdsWWqnmhRV/VmC1Pa5SBuYN6gX6dPukmsCvgLpiM1Js5wzkdPxCKhaPLfpqq5L ck1WYoCLmbtvmnwhiruP2SM7M96gq6KI/y9oEcJfKjOxp1QAcM2cJzfRTEKX3z9xFMCo clWDgNRLj0D41jYSmt+ow9mNQ7FpewWFt4PNihgklNwdNmzKiB/0L5lUCnhEURf/DYGV fQQfneo455l8dIcOE95cALWLtIzcDWJcMfL1lWYaA8JTeyuJC2qDMKiGjraN6jZIi/RS JqRw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:organization:autocrypt:from:references:cc:to:subject :dkim-signature; bh=fkHeC0QBJUdk7vZhqe39CYqplGbutdV8Iag/eDZdyIQ=; b=A2BA0BJxivegidn1LKDDjdyNLXZy57+G2gb0Z6BA7dAQN2BdaIzJ6fV51koyJe4INl ItWMOM8ycgKy9DyUIjbfj8oRI58cSd3u1YmxWiLGvm8dFIUUMnnjylg/6asfBYpQscpt XtoU/aWEmDc+rwWlqK2qxMsuEFjdXsePPP65wI89Gg7MESmEO/jeaqQXnZTFTmFbzFMa 3fb2prFx2JkfVzv6fFVN2T3DPRJN+mfyLmcbagsMcWnHFg0WfNf081Lg9SIaxEKCb0V1 hSio+pUUWnWHt7JbkTq+8q/zo/MIB8/QnGtmeu0hTR+QhmiQp6hSZLcMtnW4wO2u0+J/ PeMw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=MtqJ+7ld; 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=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id t19si15603367ejx.443.2020.07.08.03.05.31; Wed, 08 Jul 2020 03:05:54 -0700 (PDT) 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=@redhat.com header.s=mimecast20190719 header.b=MtqJ+7ld; 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=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728547AbgGHKEf (ORCPT + 99 others); Wed, 8 Jul 2020 06:04:35 -0400 Received: from us-smtp-1.mimecast.com ([205.139.110.61]:51454 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728169AbgGHKEe (ORCPT ); Wed, 8 Jul 2020 06:04:34 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1594202672; 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:autocrypt:autocrypt; bh=fkHeC0QBJUdk7vZhqe39CYqplGbutdV8Iag/eDZdyIQ=; b=MtqJ+7ldWFRwv6PY+bg1xLyL3O0u129Ec+d61nYfOsOgzuPz2UYSd5mqec7Q73kt7EQuRa bOqD9y1cpt75tI46zlYK6DObr5DDE2QTn/WUxselKxOrD0wUEfclsXntBrAjvcI5Fm1Wyk 97BlLImr+NZIrPDh0/HC4tle5yo9bDY= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-36-X6kz7XnkNSG7LKZB3xj5Ig-1; Wed, 08 Jul 2020 06:04:28 -0400 X-MC-Unique: X6kz7XnkNSG7LKZB3xj5Ig-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 544B31080; Wed, 8 Jul 2020 10:04:26 +0000 (UTC) Received: from [10.36.113.117] (ovpn-113-117.ams2.redhat.com [10.36.113.117]) by smtp.corp.redhat.com (Postfix) with ESMTP id D96AD60CD1; Wed, 8 Jul 2020 10:04:22 +0000 (UTC) Subject: Re: [PATCH v2 1/3] arm64/numa: export memory_add_physaddr_to_nid as EXPORT_SYMBOL_GPL To: Mike Rapoport Cc: Mike Rapoport , Dan Williams , Michal Hocko , Jia He , Catalin Marinas , Will Deacon , Vishal Verma , Dave Jiang , Andrew Morton , Baoquan He , Chuhong Yuan , Linux ARM , Linux Kernel Mailing List , Linux MM , linux-nvdimm , Kaly Xin References: <20200707180043.GA386073@linux.ibm.com> <20200708052626.GB386073@linux.ibm.com> <9a009cf6-6c30-91ca-a1a5-9aa090c66631@redhat.com> <999ea296-4695-1219-6a4d-a027718f61e5@redhat.com> <20200708083951.GH386073@linux.ibm.com> <20200708091520.GE128651@kernel.org> <20200708094549.GA781326@linux.ibm.com> From: David Hildenbrand Autocrypt: addr=david@redhat.com; prefer-encrypt=mutual; keydata= mQINBFXLn5EBEAC+zYvAFJxCBY9Tr1xZgcESmxVNI/0ffzE/ZQOiHJl6mGkmA1R7/uUpiCjJ dBrn+lhhOYjjNefFQou6478faXE6o2AhmebqT4KiQoUQFV4R7y1KMEKoSyy8hQaK1umALTdL QZLQMzNE74ap+GDK0wnacPQFpcG1AE9RMq3aeErY5tujekBS32jfC/7AnH7I0v1v1TbbK3Gp XNeiN4QroO+5qaSr0ID2sz5jtBLRb15RMre27E1ImpaIv2Jw8NJgW0k/D1RyKCwaTsgRdwuK Kx/Y91XuSBdz0uOyU/S8kM1+ag0wvsGlpBVxRR/xw/E8M7TEwuCZQArqqTCmkG6HGcXFT0V9 PXFNNgV5jXMQRwU0O/ztJIQqsE5LsUomE//bLwzj9IVsaQpKDqW6TAPjcdBDPLHvriq7kGjt WhVhdl0qEYB8lkBEU7V2Yb+SYhmhpDrti9Fq1EsmhiHSkxJcGREoMK/63r9WLZYI3+4W2rAc UucZa4OT27U5ZISjNg3Ev0rxU5UH2/pT4wJCfxwocmqaRr6UYmrtZmND89X0KigoFD/XSeVv jwBRNjPAubK9/k5NoRrYqztM9W6sJqrH8+UWZ1Idd/DdmogJh0gNC0+N42Za9yBRURfIdKSb B3JfpUqcWwE7vUaYrHG1nw54pLUoPG6sAA7Mehl3nd4pZUALHwARAQABtCREYXZpZCBIaWxk ZW5icmFuZCA8ZGF2aWRAcmVkaGF0LmNvbT6JAlgEEwEIAEICGwMFCQlmAYAGCwkIBwMCBhUI AgkKCwQWAgMBAh4BAheAFiEEG9nKrXNcTDpGDfzKTd4Q9wD/g1oFAl3pImkCGQEACgkQTd4Q 9wD/g1o+VA//SFvIHUAvul05u6wKv/pIR6aICPdpF9EIgEU448g+7FfDgQwcEny1pbEzAmiw zAXIQ9H0NZh96lcq+yDLtONnXk/bEYWHHUA014A1wqcYNRY8RvY1+eVHb0uu0KYQoXkzvu+s Dncuguk470XPnscL27hs8PgOP6QjG4jt75K2LfZ0eAqTOUCZTJxA8A7E9+XTYuU0hs7QVrWJ jQdFxQbRMrYz7uP8KmTK9/Cnvqehgl4EzyRaZppshruKMeyheBgvgJd5On1wWq4ZUV5PFM4x II3QbD3EJfWbaJMR55jI9dMFa+vK7MFz3rhWOkEx/QR959lfdRSTXdxs8V3zDvChcmRVGN8U Vo93d1YNtWnA9w6oCW1dnDZ4kgQZZSBIjp6iHcA08apzh7DPi08jL7M9UQByeYGr8KuR4i6e RZI6xhlZerUScVzn35ONwOC91VdYiQgjemiVLq1WDDZ3B7DIzUZ4RQTOaIWdtXBWb8zWakt/ ztGhsx0e39Gvt3391O1PgcA7ilhvqrBPemJrlb9xSPPRbaNAW39P8ws/UJnzSJqnHMVxbRZC Am4add/SM+OCP0w3xYss1jy9T+XdZa0lhUvJfLy7tNcjVG/sxkBXOaSC24MFPuwnoC9WvCVQ ZBxouph3kqc4Dt5X1EeXVLeba+466P1fe1rC8MbcwDkoUo65Ag0EVcufkQEQAOfX3n0g0fZz Bgm/S2zF/kxQKCEKP8ID+Vz8sy2GpDvveBq4H2Y34XWsT1zLJdvqPI4af4ZSMxuerWjXbVWb T6d4odQIG0fKx4F8NccDqbgHeZRNajXeeJ3R7gAzvWvQNLz4piHrO/B4tf8svmRBL0ZB5P5A 2uhdwLU3NZuK22zpNn4is87BPWF8HhY0L5fafgDMOqnf4guJVJPYNPhUFzXUbPqOKOkL8ojk CXxkOFHAbjstSK5Ca3fKquY3rdX3DNo+EL7FvAiw1mUtS+5GeYE+RMnDCsVFm/C7kY8c2d0G NWkB9pJM5+mnIoFNxy7YBcldYATVeOHoY4LyaUWNnAvFYWp08dHWfZo9WCiJMuTfgtH9tc75 7QanMVdPt6fDK8UUXIBLQ2TWr/sQKE9xtFuEmoQGlE1l6bGaDnnMLcYu+Asp3kDT0w4zYGsx 5r6XQVRH4+5N6eHZiaeYtFOujp5n+pjBaQK7wUUjDilPQ5QMzIuCL4YjVoylWiBNknvQWBXS lQCWmavOT9sttGQXdPCC5ynI+1ymZC1ORZKANLnRAb0NH/UCzcsstw2TAkFnMEbo9Zu9w7Kv AxBQXWeXhJI9XQssfrf4Gusdqx8nPEpfOqCtbbwJMATbHyqLt7/oz/5deGuwxgb65pWIzufa N7eop7uh+6bezi+rugUI+w6DABEBAAGJAiUEGAECAA8FAlXLn5ECGwwFCQlmAYAACgkQTd4Q 9wD/g1qA6w/+M+ggFv+JdVsz5+ZIc6MSyGUozASX+bmIuPeIecc9UsFRatc91LuJCKMkD9Uv GOcWSeFpLrSGRQ1Z7EMzFVU//qVs6uzhsNk0RYMyS0B6oloW3FpyQ+zOVylFWQCzoyyf227y GW8HnXunJSC+4PtlL2AY4yZjAVAPLK2l6mhgClVXTQ/S7cBoTQKP+jvVJOoYkpnFxWE9pn4t H5QIFk7Ip8TKr5k3fXVWk4lnUi9MTF/5L/mWqdyIO1s7cjharQCstfWCzWrVeVctpVoDfJWp 4LwTuQ5yEM2KcPeElLg5fR7WB2zH97oI6/Ko2DlovmfQqXh9xWozQt0iGy5tWzh6I0JrlcxJ ileZWLccC4XKD1037Hy2FLAjzfoWgwBLA6ULu0exOOdIa58H4PsXtkFPrUF980EEibUp0zFz GotRVekFAceUaRvAj7dh76cToeZkfsjAvBVb4COXuhgX6N4pofgNkW2AtgYu1nUsPAo+NftU CxrhjHtLn4QEBpkbErnXQyMjHpIatlYGutVMS91XTQXYydCh5crMPs7hYVsvnmGHIaB9ZMfB njnuI31KBiLUks+paRkHQlFcgS2N3gkRBzH7xSZ+t7Re3jvXdXEzKBbQ+dC3lpJB0wPnyMcX FOTT3aZT7IgePkt5iC/BKBk3hqKteTnJFeVIT7EC+a6YUFg= Organization: Red Hat GmbH Message-ID: <98166184-3aaf-479e-bfb3-fc737f4ac98d@redhat.com> Date: Wed, 8 Jul 2020 12:04:21 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0 MIME-Version: 1.0 In-Reply-To: <20200708094549.GA781326@linux.ibm.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 08.07.20 11:45, Mike Rapoport wrote: > On Wed, Jul 08, 2020 at 11:25:36AM +0200, David Hildenbrand wrote: >> On 08.07.20 11:15, Mike Rapoport wrote: >>>>>>>> >>>>> But on more theoretical/fundmanetal level, I think we lack a generic >>>>> abstraction similar to e.g. x86 'struct numa_meminfo' that serves as >>>>> translaton of firmware supplied information into data that can be used >>>>> by the generic mm without need to reimplement it for each and every >>>>> arch. >>>> >>>> Right. As I expressed, I am not a friend of using memblock for that, and >>>> the pgdat node span is tricky. >>>> >>>> Maybe abstracting that x86 concept is possible in some way (and we could >>>> restrict the information to boot-time properties, so we don't have to >>>> mess with memory hot(un)plug - just as done for numa_meminfo AFAIKS). >>> >>> I agree with pgdat part and disagree about memblock. It already has >>> non-init physmap, why won't we add memblock.memory to the mix? ;-) >> >> Can we generalize and tweak physmap to contain node info? That's all we >> need, no? (the special mem= parameter handling should not matter for our >> use case, where "physmap" and "memory" would differ) > > TBH, I have only random vague thoughts at the moment. This might be an > option. But then we need to enable physmap on !s390, right? Yes, looks like it. > >>> Now, seriously, memblock already has all the necessary information about >>> the coldplug memory for several architectures. x86 being an exception >>> because for some reason the reserved memory is not considered memory >>> there. The infrastructure for quiering and iterating memory regions is >>> already there. We just need to leave out the irrelevant parts, like >>> memblock.reserved and allocation funcions. >> >> I *really* don't want to mess with memblocks on memory hot(un)plug on >> x86 and s390x (+other architectures in the future). I also thought about >> stopping to create memblocks for hotplugged memory on arm64, by tweaking >> pfn_valid() to query memblocks only for early sections. >> >> If "physmem" is not an option, can we at least introduce something like >> ARCH_UPDTAE_MEMBLOCK_ON_HOTPLUG to avoid doing that on x86 and s390x for >> now (and later maybe for others)? > > I have to do more memory hotplug howework to answer that ;-) > > My general point is that we don't have to reinvent the wheel to have > coldplug memory representation, it's already there. We just need a way > to use it properly. Yes, I tend to agree. Details to be clarified :) -- Thanks, David / dhildenb