Received: by 2002:a25:e74b:0:0:0:0:0 with SMTP id e72csp1073924ybh; Mon, 13 Jul 2020 08:43:39 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzmjdvWQNUHad/JO8cDgAB4vLW0bDebub/VwPbYrM7HFjciJ+Vr+FGd8Yy6pjdlciqHCAUp X-Received: by 2002:a17:906:1688:: with SMTP id s8mr386023ejd.164.1594655019593; Mon, 13 Jul 2020 08:43:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1594655019; cv=none; d=google.com; s=arc-20160816; b=aiEY1Pv5WncGMeeDL+RS8+aPZVpsznSsiBF63IjUCI6XxxXOMRpifmhix5oq/1PLsS BQz+/9glXohyGSN2yiJL6f81aeG6AGInhpXweVuqFU3fH+oD5naN0+Y/YoDCBrdBp4F+ n8IDY5wfL+1YViLTFADfhxZA2VP0TlVQss0E+RNFPZJ8GpZJPNHdKe1j1N1dL4IUDY7p qM054iKk+OdJ4l4vCzWUuM7VvnvPB6rj/7lxGiaFoZUiQ7hawmrsOUc4g4cY1h64/Ya6 9eXvE8a4gXWWF69MGDlKZOHz8JV9I8Zvjn9rS+jdtv6Ji7ulIszCoacCp9emcYnsAC2e xGRg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=KYHsayQ+qnaeJrGEqb3AbWD3OCs6eDEgmK0sEjz5stk=; b=Q8ZN1Hj37JeoVNsxXD0DB4U934DHxauDyaxDy9QjleCbgWeKzcQCuq1qZesA0yQrRY GCz5O4IdcqGi5wWYwLaEF+biDkfGCk6fjGwHIK+nhlBJj2KXdo//lHMMHQi7ikGNqrB8 xOo5GU1w2X63ySOpA8RewIZq75mqXwt2wqni0EAv8Oy6fzjIWJkxYKUxwXstDYw1VPQp wlRqNORBGWIjl7z8Kh+n+m7mZ0ba+iPS98yBrvXrqwjjbpAMHJDhvVkQ4eq6EFWP0sV6 lSBNu0VysRvlfiEnyee8b1uRSSZvlHGK5AAPmSICheSHhrqNkCkkSws9S36Kul4XVyBV e5xQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel-com.20150623.gappssmtp.com header.s=20150623 header.b=shNHxqlE; 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=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id u11si10166089edy.592.2020.07.13.08.43.16; Mon, 13 Jul 2020 08:43:39 -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=@intel-com.20150623.gappssmtp.com header.s=20150623 header.b=shNHxqlE; 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=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730119AbgGMPm4 (ORCPT + 99 others); Mon, 13 Jul 2020 11:42:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40980 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730029AbgGMPmx (ORCPT ); Mon, 13 Jul 2020 11:42:53 -0400 Received: from mail-ej1-x643.google.com (mail-ej1-x643.google.com [IPv6:2a00:1450:4864:20::643]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 041FBC08C5DE for ; Mon, 13 Jul 2020 08:42:53 -0700 (PDT) Received: by mail-ej1-x643.google.com with SMTP id w6so17736295ejq.6 for ; Mon, 13 Jul 2020 08:42:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intel-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=KYHsayQ+qnaeJrGEqb3AbWD3OCs6eDEgmK0sEjz5stk=; b=shNHxqlEshcLM+d6HS5/rUuF/G7IfTpZe/gUMK2OQCtYZavKPmFx9lPmSy+8XWB0KK 35jBVVrUdNO+Jfvrrp+eIP/JvR08WY9U0DdkU6T89bTgCxQCuK1PVuWJIjGMTLjE8rE3 XTJ5PHCfIDj2m3E204SFtns5sNa6dcgofuJWbiwgwOmwi0NipOUB6QrkLZ+DoEueqmMB PgWCgNO4So36JTX6IgokxC3NYAKVD194ZFfivEOk1MU5Ch8Hq+JnhQK68aoXqc58zKh0 6H4qLbRrffd4vFYKWrXDmxbjRxZ7jEpY4zZCg4XrAX2YN8jpDHcMkBByyN832GpItPwM QGlQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=KYHsayQ+qnaeJrGEqb3AbWD3OCs6eDEgmK0sEjz5stk=; b=WiNFarKIGmEr4dqvYq8IKTFFM3N+1JTwj3hh17V+Lebnhj5QcU7l/5045tCqWyWW4C b1zyvcNeTMPiGHPRaWyFCJ5w/uxRT/OtH1pBZbd0iO/x9x9Wp3Duu3juCz567fPPAZda zeR0GrZKcOXmSfnKwrwtefhXw0Pht5dSWYZALhiAebTBvd6Kx4sNntKawk5jbwKD1+af YJ6b8A4d6D6ZJ2lq7gT/UdRMy6xq1lMfqjB2PkmCLoYBB+Wss7Hy2Ywtee1PqCZEGugI xnWJhgK2HGSpFX68nA7ITwzBa96nAl0oy14QqqdJh8F4eQGLBhOFBDd/jKm7nN9A42eJ Smnw== X-Gm-Message-State: AOAM530MAC3ebxS0NxWTNc/W3GmuOZdTmt8qTUIpHair9MmVKYy+pS8i RAlIIFZLd75n11yfWBs1MKRJwa+N5+g8Hgc/6yYRvOWQ X-Received: by 2002:a17:907:20af:: with SMTP id pw15mr393528ejb.204.1594654971733; Mon, 13 Jul 2020 08:42:51 -0700 (PDT) MIME-Version: 1.0 References: <159457116473.754248.7879464730875147365.stgit@dwillia2-desk3.amr.corp.intel.com> <159457120334.754248.12908401960465408733.stgit@dwillia2-desk3.amr.corp.intel.com> <20200713065801.GB11000@linux.ibm.com> In-Reply-To: <20200713065801.GB11000@linux.ibm.com> From: Dan Williams Date: Mon, 13 Jul 2020 08:42:41 -0700 Message-ID: Subject: Re: [PATCH v2 07/22] numa: Introduce a generic memory_add_physaddr_to_nid() To: Mike Rapoport Cc: linux-nvdimm , Jia He , Will Deacon , David Hildenbrand , Andrew Morton , Peter Zijlstra , Vishal L Verma , Dave Hansen , Ard Biesheuvel , Linux MM , Linux Kernel Mailing List , Linux ACPI , Christoph Hellwig , Joao Martins Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Jul 12, 2020 at 11:58 PM Mike Rapoport wrote: > > Hi Dan, > > On Sun, Jul 12, 2020 at 09:26:43AM -0700, Dan Williams wrote: > > For architectures that opt into storing their numa data in memblock > > (only ARM64 currently), add a memblock generic way to interrogate that > > data for memory_add_physaddr_to_nid(). This requires ARCH_KEEP_MEMBLOCK > > to keep memblock text and data around after boot. > > I afraid we are too far from using memblock as a generic placeholder for > numa data. Although all architectures now have the numa info in > memblock, only arm64 uses memblock as the primary source of that data. > > I'd rather prefer Jia's solution [1] to have a weak default for > memory_add_physaddr_to_nid() and let architectures override it. I'm ok with that as long as we do the same for phys_to_target_node(). Will had the concern about adding a generic numa-info facility the last I tried this. I just don't see a practical way to get there in the near term.