linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	 kernel test robot <lkp@intel.com>,
	Joao Martins <joao.m.martins@oracle.com>, X86 ML <x86@kernel.org>,
	 Vishal Verma <vishal.l.verma@intel.com>,
	Linux MM <linux-mm@kvack.org>,
	 linux-nvdimm <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH] x86/mm: Fix phys_to_target_node() export
Date: Fri, 30 Oct 2020 18:54:35 -0700	[thread overview]
Message-ID: <CAPcyv4iw_ZuHdhrGHUPh+iBYuO7sN_omEGb8RMmOKVzSCpbT0g@mail.gmail.com> (raw)
In-Reply-To: <160402498564.4173389.2743697400148832021.stgit@dwillia2-desk3.amr.corp.intel.com>

On Thu, Oct 29, 2020 at 7:29 PM Dan Williams <dan.j.williams@intel.com> wrote:
>
> The core-mm has a default __weak implementation of phys_to_target_node()
> when the architecture does not override it. That symbol is exported
> for modules. However, while the export in mm/memory_hotplug.c exported
> the symbol in the configuration cases of:
>
>         CONFIG_NUMA_KEEP_MEMINFO=y
>         CONFIG_MEMORY_HOTPLUG=y
>
> ...and:
>
>         CONFIG_NUMA_KEEP_MEMINFO=n
>         CONFIG_MEMORY_HOTPLUG=y
>
> ...it failed to export the symbol in the case of:
>
>         CONFIG_NUMA_KEEP_MEMINFO=y
>         CONFIG_MEMORY_HOTPLUG=n
>
> Always export the symbol from the CONFIG_NUMA_KEEP_MEMINFO section of
> arch/x86/mm/numa.c, and teach mm/memory_hotplug.c to optionally export
> in case arch/x86/mm/numa.c has already performed the export.
>
> The dependency on NUMA_KEEP_MEMINFO for DEV_DAX_HMEM_DEVICES is invalid
> now that the symbol is properly exported in all combinations of
> CONFIG_NUMA_KEEP_MEMINFO and CONFIG_MEMORY_HOTPLUG. Note that in the
> CONFIG_NUMA=n case no export is needed since their is a dummy static
> inline implementation of phys_to_target_node() in that case.
>
> Reported-by: Randy Dunlap <rdunlap@infradead.org>
> Reported-by: Thomas Gleixner <tglx@linutronix.de>
> Reported-by: kernel test robot <lkp@intel.com>
> Fixes: a035b6bf863e ("mm/memory_hotplug: introduce default phys_to_target_node() implementation")
> Cc: Joao Martins <joao.m.martins@oracle.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: x86@kernel.org
> Cc: Vishal Verma <vishal.l.verma@intel.com>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>

Thomas, do you want to ack this so Andrew can pick it up, or I can
take it through as a device-dax update, but either way the diffstat
warrants x86 + mm acks.


  parent reply	other threads:[~2020-10-31  1:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-30  2:29 [PATCH] x86/mm: Fix phys_to_target_node() export Dan Williams
2020-10-30  3:05 ` Randy Dunlap
2020-10-30 11:34 ` David Hildenbrand
2020-10-31  1:54 ` Dan Williams [this message]
2020-10-31  3:01   ` Thomas Gleixner
2020-10-31  4:45     ` Dan Williams
2020-10-31  9:10 ` Christoph Hellwig
2020-11-02 23:52   ` Dan Williams
2020-11-03  0:59     ` Randy Dunlap
2020-11-03  8:33     ` Christoph Hellwig
2020-11-03 10:39     ` Thomas Gleixner
2020-11-04  1:38     ` Andrew Morton
2020-11-04  1:49       ` Dan Williams

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPcyv4iw_ZuHdhrGHUPh+iBYuO7sN_omEGb8RMmOKVzSCpbT0g@mail.gmail.com \
    --to=dan.j.williams@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=joao.m.martins@oracle.com \
    --cc=linux-mm@kvack.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=lkp@intel.com \
    --cc=rdunlap@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=vishal.l.verma@intel.com \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).