RE: [PATCH v2 08/22] memblock: Introduce a generic phys_addr_to_target_node()

2020-07-13 Thread Justin He
heuvel > ; Linux MM ; Linux Kernel > Mailing List ; Linux ACPI a...@vger.kernel.org>; Christoph Hellwig ; Joao Martins > > Subject: Re: [PATCH v2 08/22] memblock: Introduce a generic > phys_addr_to_target_node() > > On Mon, Jul 13, 2020 at 12:04 AM Mike Rapoport wrote: > &g

Re: [PATCH v2 08/22] memblock: Introduce a generic phys_addr_to_target_node()

2020-07-13 Thread Dan Williams
On Mon, Jul 13, 2020 at 12:04 AM Mike Rapoport wrote: > > Hi Dan, > > On Sun, Jul 12, 2020 at 09:26:48AM -0700, Dan Williams wrote: > > Similar to how generic memory_add_physaddr_to_nid() interrogates > > memblock data for numa information, introduce > > get_reserved_pfn_range_from_nid() to

Re: [PATCH v2 08/22] memblock: Introduce a generic phys_addr_to_target_node()

2020-07-13 Thread Mike Rapoport
Hi Dan, On Sun, Jul 12, 2020 at 09:26:48AM -0700, Dan Williams wrote: > Similar to how generic memory_add_physaddr_to_nid() interrogates > memblock data for numa information, introduce > get_reserved_pfn_range_from_nid() to enable the same operation for > reserved memory ranges. Example memory

[PATCH v2 08/22] memblock: Introduce a generic phys_addr_to_target_node()

2020-07-12 Thread Dan Williams
Similar to how generic memory_add_physaddr_to_nid() interrogates memblock data for numa information, introduce get_reserved_pfn_range_from_nid() to enable the same operation for reserved memory ranges. Example memory ranges that are reserved, but still have associated numa-info are persistent