From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: <linux-kernel@vger.kernel.org>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Andreas Larsson <andreas@gaisler.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>, "Borislav Petkov" <bp@alien8.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Dan Williams <dan.j.williams@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
David Hildenbrand <david@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Davidlohr Bueso <dave@stgolabs.net>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
Heiko Carstens <hca@linux.ibm.com>,
Huacai Chen <chenhuacai@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
"John Paul Adrian Glaubitz" <glaubitz@physik.fu-berlin.de>,
Jonathan Corbet <corbet@lwn.net>,
Michael Ellerman <mpe@ellerman.id.au>,
Palmer Dabbelt <palmer@dabbelt.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Rob Herring <robh@kernel.org>,
Samuel Holland <samuel.holland@sifive.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Thomas Gleixner <tglx@linutronix.de>,
"Vasily Gorbik" <gor@linux.ibm.com>,
Will Deacon <will@kernel.org>, Zi Yan <ziy@nvidia.com>,
<devicetree@vger.kernel.org>, <linux-acpi@vger.kernel.org>,
<linux-arch@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-cxl@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-mips@vger.kernel.org>, <linux-mm@kvack.org>,
<linux-riscv@lists.infradead.org>, <linux-s390@vger.kernel.org>,
<linux-sh@vger.kernel.org>, <linuxppc-dev@lists.ozlabs.org>,
<loongarch@lists.linux.dev>, <nvdimm@lists.linux.dev>,
<sparclinux@vger.kernel.org>, <x86@kernel.org>
Subject: Re: [PATCH v3 11/26] x86/numa: use get_pfn_range_for_nid to verify that node spans memory
Date: Fri, 2 Aug 2024 11:36:29 +0100 [thread overview]
Message-ID: <20240802113629.00003069@Huawei.com> (raw)
In-Reply-To: <20240801060826.559858-12-rppt@kernel.org>
On Thu, 1 Aug 2024 09:08:11 +0300
Mike Rapoport <rppt@kernel.org> wrote:
> From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
>
> Instead of looping over numa_meminfo array to detect node's start and
> end addresses use get_pfn_range_for_init().
>
> This is shorter and make it easier to lift numa_memblks to generic code.
>
> Signed-off-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> Tested-by: Zi Yan <ziy@nvidia.com> # for x86_64 and arm64
Fair enough given code a few lines up has set the node
for all the memblocks so this should I think give the same
effective result.
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> ---
> arch/x86/mm/numa.c | 13 +++----------
> 1 file changed, 3 insertions(+), 10 deletions(-)
>
> diff --git a/arch/x86/mm/numa.c b/arch/x86/mm/numa.c
> index edfc38803779..cfe7e5477cf8 100644
> --- a/arch/x86/mm/numa.c
> +++ b/arch/x86/mm/numa.c
> @@ -521,17 +521,10 @@ static int __init numa_register_memblks(struct numa_meminfo *mi)
>
> /* Finally register nodes. */
> for_each_node_mask(nid, node_possible_map) {
> - u64 start = PFN_PHYS(max_pfn);
> - u64 end = 0;
> + unsigned long start_pfn, end_pfn;
>
> - for (i = 0; i < mi->nr_blks; i++) {
> - if (nid != mi->blk[i].nid)
> - continue;
> - start = min(mi->blk[i].start, start);
> - end = max(mi->blk[i].end, end);
> - }
> -
> - if (start >= end)
> + get_pfn_range_for_nid(nid, &start_pfn, &end_pfn);
> + if (start_pfn >= end_pfn)
> continue;
>
> alloc_node_data(nid);
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: <linux-kernel@vger.kernel.org>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Andreas Larsson <andreas@gaisler.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>, "Borislav Petkov" <bp@alien8.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Dan Williams <dan.j.williams@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
David Hildenbrand <david@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Davidlohr Bueso <dave@stgolabs.net>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
Heiko Carstens <hca@linux.ibm.com>,
Huacai Chen <chenhuacai@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
"John Paul Adrian Glaubitz" <glaubitz@physik.fu-berlin.de>,
Jonathan Corbet <corbet@lwn.net>,
Michael Ellerman <mpe@ellerman.id.au>,
Palmer Dabbelt <palmer@dabbelt.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Rob Herring <robh@kernel.org>,
Samuel Holland <samuel.holland@sifive.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Thomas Gleixner <tglx@linutronix.de>,
"Vasily Gorbik" <gor@linux.ibm.com>,
Will Deacon <will@kernel.org>, Zi Yan <ziy@nvidia.com>,
<devicetree@vger.kernel.org>, <linux-acpi@vger.kernel.org>,
<linux-arch@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-cxl@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-mips@vger.kernel.org>, <linux-mm@kvack.org>,
<linux-riscv@lists.infradead.org>, <linux-s390@vger.kernel.org>,
<linux-sh@vger.kernel.org>, <linuxppc-dev@lists.ozlabs.org>,
<loongarch@lists.linux.dev>, <nvdimm@lists.linux.dev>,
<sparclinux@vger.kernel.org>, <x86@kernel.org>
Subject: Re: [PATCH v3 11/26] x86/numa: use get_pfn_range_for_nid to verify that node spans memory
Date: Fri, 2 Aug 2024 11:36:29 +0100 [thread overview]
Message-ID: <20240802113629.00003069@Huawei.com> (raw)
In-Reply-To: <20240801060826.559858-12-rppt@kernel.org>
On Thu, 1 Aug 2024 09:08:11 +0300
Mike Rapoport <rppt@kernel.org> wrote:
> From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
>
> Instead of looping over numa_meminfo array to detect node's start and
> end addresses use get_pfn_range_for_init().
>
> This is shorter and make it easier to lift numa_memblks to generic code.
>
> Signed-off-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> Tested-by: Zi Yan <ziy@nvidia.com> # for x86_64 and arm64
Fair enough given code a few lines up has set the node
for all the memblocks so this should I think give the same
effective result.
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> ---
> arch/x86/mm/numa.c | 13 +++----------
> 1 file changed, 3 insertions(+), 10 deletions(-)
>
> diff --git a/arch/x86/mm/numa.c b/arch/x86/mm/numa.c
> index edfc38803779..cfe7e5477cf8 100644
> --- a/arch/x86/mm/numa.c
> +++ b/arch/x86/mm/numa.c
> @@ -521,17 +521,10 @@ static int __init numa_register_memblks(struct numa_meminfo *mi)
>
> /* Finally register nodes. */
> for_each_node_mask(nid, node_possible_map) {
> - u64 start = PFN_PHYS(max_pfn);
> - u64 end = 0;
> + unsigned long start_pfn, end_pfn;
>
> - for (i = 0; i < mi->nr_blks; i++) {
> - if (nid != mi->blk[i].nid)
> - continue;
> - start = min(mi->blk[i].start, start);
> - end = max(mi->blk[i].end, end);
> - }
> -
> - if (start >= end)
> + get_pfn_range_for_nid(nid, &start_pfn, &end_pfn);
> + if (start_pfn >= end_pfn)
> continue;
>
> alloc_node_data(nid);
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: nvdimm@lists.linux.dev, x86@kernel.org,
Andreas Larsson <andreas@gaisler.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
David Hildenbrand <david@redhat.com>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
linux-mips@vger.kernel.org, linux-mm@kvack.org,
sparclinux@vger.kernel.org,
Alexander Gordeev <agordeev@linux.ibm.com>,
Will Deacon <will@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-arch@vger.kernel.org, Rob Herring <robh@kernel.org>,
Davidlohr Bueso <dave@stgolabs.net>,
Vasily Gorbik <gor@linux.ibm.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-sh@vger.kernel.org, Huacai Chen <chenhuacai@kernel.org>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
linux-acpi@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Zi Yan <ziy@nvidia.com>,
devicetree@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
linux-s390@vger.kernel.org, Heiko Carstens <hca@linux.ibm.com>,
Borislav Petkov <bp@alien8.de>,
linux-cxl@vger.kernel.org, loongarch@lists.linux.dev,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Dan Williams <dan.j.williams@intel.com>,
linux-arm-kernel@lists.infradead.org,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Samuel Holland <samuel.holland@sifive.com>,
linux-riscv@lists.infradead.org,
Palmer Dabbelt <palmer@dabbelt.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linuxppc-dev@lists.ozlabs.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH v3 11/26] x86/numa: use get_pfn_range_for_nid to verify that node spans memory
Date: Fri, 2 Aug 2024 11:36:29 +0100 [thread overview]
Message-ID: <20240802113629.00003069@Huawei.com> (raw)
In-Reply-To: <20240801060826.559858-12-rppt@kernel.org>
On Thu, 1 Aug 2024 09:08:11 +0300
Mike Rapoport <rppt@kernel.org> wrote:
> From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
>
> Instead of looping over numa_meminfo array to detect node's start and
> end addresses use get_pfn_range_for_init().
>
> This is shorter and make it easier to lift numa_memblks to generic code.
>
> Signed-off-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> Tested-by: Zi Yan <ziy@nvidia.com> # for x86_64 and arm64
Fair enough given code a few lines up has set the node
for all the memblocks so this should I think give the same
effective result.
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> ---
> arch/x86/mm/numa.c | 13 +++----------
> 1 file changed, 3 insertions(+), 10 deletions(-)
>
> diff --git a/arch/x86/mm/numa.c b/arch/x86/mm/numa.c
> index edfc38803779..cfe7e5477cf8 100644
> --- a/arch/x86/mm/numa.c
> +++ b/arch/x86/mm/numa.c
> @@ -521,17 +521,10 @@ static int __init numa_register_memblks(struct numa_meminfo *mi)
>
> /* Finally register nodes. */
> for_each_node_mask(nid, node_possible_map) {
> - u64 start = PFN_PHYS(max_pfn);
> - u64 end = 0;
> + unsigned long start_pfn, end_pfn;
>
> - for (i = 0; i < mi->nr_blks; i++) {
> - if (nid != mi->blk[i].nid)
> - continue;
> - start = min(mi->blk[i].start, start);
> - end = max(mi->blk[i].end, end);
> - }
> -
> - if (start >= end)
> + get_pfn_range_for_nid(nid, &start_pfn, &end_pfn);
> + if (start_pfn >= end_pfn)
> continue;
>
> alloc_node_data(nid);
next prev parent reply other threads:[~2024-08-02 10:53 UTC|newest]
Thread overview: 243+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 6:08 [PATCH v3 00/26] mm: introduce numa_memblks Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` [PATCH v3 01/26] mm: move kernel/numa.c to mm/ Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` [PATCH v3 02/26] MIPS: sgi-ip27: make NODE_DATA() the same as on all other architectures Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 17:44 ` Jonathan Cameron
2024-08-01 17:44 ` Jonathan Cameron
2024-08-01 17:44 ` Jonathan Cameron
2024-08-06 13:05 ` David Hildenbrand
2024-08-06 13:05 ` David Hildenbrand
2024-08-06 13:05 ` David Hildenbrand
2024-08-01 6:08 ` [PATCH v3 03/26] MIPS: sgi-ip27: ensure node_possible_map only contains valid nodes Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 17:44 ` Jonathan Cameron
2024-08-01 17:44 ` Jonathan Cameron
2024-08-01 17:44 ` Jonathan Cameron
2024-08-06 13:05 ` David Hildenbrand
2024-08-06 13:05 ` David Hildenbrand
2024-08-06 13:05 ` David Hildenbrand
2024-08-01 6:08 ` [PATCH v3 04/26] MIPS: sgi-ip27: drop HAVE_ARCH_NODEDATA_EXTENSION Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 17:45 ` Jonathan Cameron
2024-08-01 17:45 ` Jonathan Cameron
2024-08-01 17:45 ` Jonathan Cameron
2024-08-06 13:06 ` David Hildenbrand
2024-08-06 13:06 ` David Hildenbrand
2024-08-06 13:06 ` David Hildenbrand
2024-08-01 6:08 ` [PATCH v3 05/26] MIPS: loongson64: rename __node_data to node_data Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` [PATCH v3 06/26] MIPS: loongson64: drop HAVE_ARCH_NODEDATA_EXTENSION Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 17:47 ` Jonathan Cameron
2024-08-01 17:47 ` Jonathan Cameron
2024-08-01 17:47 ` Jonathan Cameron
2024-08-06 13:07 ` David Hildenbrand
2024-08-06 13:07 ` David Hildenbrand
2024-08-06 13:07 ` David Hildenbrand
2024-08-01 6:08 ` [PATCH v3 07/26] mm: drop CONFIG_HAVE_ARCH_NODEDATA_EXTENSION Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-02 9:49 ` Jonathan Cameron
2024-08-02 9:49 ` Jonathan Cameron
2024-08-02 9:49 ` Jonathan Cameron
2024-08-03 18:58 ` Andrew Morton
2024-08-03 18:58 ` Andrew Morton
2024-08-03 18:58 ` Andrew Morton
2024-08-04 7:24 ` Mike Rapoport
2024-08-04 7:24 ` Mike Rapoport
2024-08-04 7:24 ` Mike Rapoport
2024-08-04 15:11 ` Jonathan Cameron
2024-08-04 15:11 ` Jonathan Cameron
2024-08-04 15:11 ` Jonathan Cameron
2024-08-05 14:39 ` Mike Rapoport
2024-08-05 14:39 ` Mike Rapoport
2024-08-05 14:39 ` Mike Rapoport
2024-08-01 6:08 ` [PATCH v3 08/26] arch, mm: move definition of node_data to generic code Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` [PATCH v3 09/26] arch, mm: pull out allocation of NODE_DATA " Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-02 9:55 ` Jonathan Cameron
2024-08-02 9:55 ` Jonathan Cameron
2024-08-02 9:55 ` Jonathan Cameron
2024-08-05 17:15 ` Mike Rapoport
2024-08-05 17:15 ` Mike Rapoport
2024-08-05 17:15 ` Mike Rapoport
2024-08-01 6:08 ` [PATCH v3 10/26] x86/numa: simplify numa_distance allocation Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-02 9:56 ` Jonathan Cameron
2024-08-02 9:56 ` Jonathan Cameron
2024-08-02 9:56 ` Jonathan Cameron
2024-08-06 13:08 ` David Hildenbrand
2024-08-06 13:08 ` David Hildenbrand
2024-08-06 13:08 ` David Hildenbrand
2024-08-01 6:08 ` [PATCH v3 11/26] x86/numa: use get_pfn_range_for_nid to verify that node spans memory Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-02 10:36 ` Jonathan Cameron [this message]
2024-08-02 10:36 ` Jonathan Cameron
2024-08-02 10:36 ` Jonathan Cameron
2024-08-05 20:03 ` Dan Williams
2024-08-05 20:03 ` Dan Williams
2024-08-05 20:03 ` Dan Williams
2024-08-05 20:35 ` Mike Rapoport
2024-08-05 20:35 ` Mike Rapoport
2024-08-05 20:35 ` Mike Rapoport
2024-08-06 13:10 ` David Hildenbrand
2024-08-06 13:10 ` David Hildenbrand
2024-08-06 13:10 ` David Hildenbrand
2024-08-01 6:08 ` [PATCH v3 12/26] x86/numa: move FAKE_NODE_* defines to numa_emu Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-06 13:10 ` David Hildenbrand
2024-08-06 13:10 ` David Hildenbrand
2024-08-06 13:10 ` David Hildenbrand
2024-08-01 6:08 ` [PATCH v3 13/26] x86/numa_emu: simplify allocation of phys_dist Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-06 13:11 ` David Hildenbrand
2024-08-06 13:11 ` David Hildenbrand
2024-08-06 13:11 ` David Hildenbrand
2024-08-01 6:08 ` [PATCH v3 14/26] x86/numa_emu: split __apicid_to_node update to a helper function Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-06 13:13 ` David Hildenbrand
2024-08-06 13:13 ` David Hildenbrand
2024-08-06 13:13 ` David Hildenbrand
2024-08-01 6:08 ` [PATCH v3 15/26] x86/numa_emu: use a helper function to get MAX_DMA32_PFN Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-06 13:14 ` David Hildenbrand
2024-08-06 13:14 ` David Hildenbrand
2024-08-06 13:14 ` David Hildenbrand
2024-08-01 6:08 ` [PATCH v3 16/26] x86/numa: numa_{add,remove}_cpu: make cpu parameter unsigned Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-06 13:14 ` David Hildenbrand
2024-08-06 13:14 ` David Hildenbrand
2024-08-06 13:14 ` David Hildenbrand
2024-08-01 6:08 ` [PATCH v3 17/26] mm: introduce numa_memblks Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-02 10:49 ` Jonathan Cameron
2024-08-02 10:49 ` Jonathan Cameron
2024-08-02 10:49 ` Jonathan Cameron
2024-08-06 13:16 ` David Hildenbrand
2024-08-06 13:16 ` David Hildenbrand
2024-08-06 13:16 ` David Hildenbrand
2024-08-01 6:08 ` [PATCH v3 18/26] mm: move numa_distance and related code from x86 to numa_memblks Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-02 10:52 ` Jonathan Cameron
2024-08-02 10:52 ` Jonathan Cameron
2024-08-02 10:52 ` Jonathan Cameron
2024-08-06 13:16 ` David Hildenbrand
2024-08-06 13:16 ` David Hildenbrand
2024-08-06 13:16 ` David Hildenbrand
2024-08-01 6:08 ` [PATCH v3 19/26] mm: introduce numa_emulation Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-02 11:19 ` Jonathan Cameron
2024-08-02 11:19 ` Jonathan Cameron
2024-08-02 11:19 ` Jonathan Cameron
2024-08-05 20:09 ` Dan Williams
2024-08-05 20:09 ` Dan Williams
2024-08-05 20:09 ` Dan Williams
2024-08-06 13:18 ` David Hildenbrand
2024-08-06 13:18 ` David Hildenbrand
2024-08-06 13:18 ` David Hildenbrand
2024-08-06 13:20 ` David Hildenbrand
2024-08-06 13:20 ` David Hildenbrand
2024-08-06 13:20 ` David Hildenbrand
2024-08-06 13:24 ` David Hildenbrand
2024-08-06 13:24 ` David Hildenbrand
2024-08-06 13:24 ` David Hildenbrand
2024-08-01 6:08 ` [PATCH v3 20/26] mm: numa_memblks: introduce numa_memblks_init Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-02 11:08 ` Jonathan Cameron
2024-08-02 11:08 ` Jonathan Cameron
2024-08-02 11:08 ` Jonathan Cameron
2024-08-06 13:21 ` David Hildenbrand
2024-08-06 13:21 ` David Hildenbrand
2024-08-06 13:21 ` David Hildenbrand
2024-08-01 6:08 ` [PATCH v3 21/26] mm: numa_memblks: make several functions and variables static Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-02 11:10 ` Jonathan Cameron
2024-08-02 11:10 ` Jonathan Cameron
2024-08-02 11:10 ` Jonathan Cameron
2024-08-06 13:21 ` David Hildenbrand
2024-08-06 13:21 ` David Hildenbrand
2024-08-06 13:21 ` David Hildenbrand
2024-08-01 6:08 ` [PATCH v3 22/26] mm: numa_memblks: use memblock_{start,end}_of_DRAM() when sanitizing meminfo Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-02 11:12 ` Jonathan Cameron
2024-08-02 11:12 ` Jonathan Cameron
2024-08-02 11:12 ` Jonathan Cameron
2024-08-05 20:21 ` Dan Williams
2024-08-05 20:21 ` Dan Williams
2024-08-05 20:21 ` Dan Williams
2024-08-05 20:33 ` Mike Rapoport
2024-08-05 20:33 ` Mike Rapoport
2024-08-05 20:33 ` Mike Rapoport
2024-08-06 13:22 ` David Hildenbrand
2024-08-06 13:22 ` David Hildenbrand
2024-08-06 13:22 ` David Hildenbrand
2024-08-01 6:08 ` [PATCH v3 23/26] of, numa: return -EINVAL when no numa-node-id is found Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-02 14:01 ` Jonathan Cameron
2024-08-02 14:01 ` Jonathan Cameron
2024-08-02 14:01 ` Jonathan Cameron
2024-08-06 13:23 ` David Hildenbrand
2024-08-06 13:23 ` David Hildenbrand
2024-08-06 13:23 ` David Hildenbrand
2024-08-01 6:08 ` [PATCH v3 24/26] arch_numa: switch over to numa_memblks Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-02 15:07 ` Jonathan Cameron
2024-08-02 15:07 ` Jonathan Cameron
2024-08-02 15:07 ` Jonathan Cameron
2024-08-06 13:28 ` David Hildenbrand
2024-08-06 13:28 ` David Hildenbrand
2024-08-06 13:28 ` David Hildenbrand
2024-08-01 6:08 ` [PATCH v3 25/26] mm: make range-to-target_node lookup facility a part of numa_memblks Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-05 20:24 ` Dan Williams
2024-08-05 20:24 ` Dan Williams
2024-08-05 20:24 ` Dan Williams
2024-08-06 13:27 ` David Hildenbrand
2024-08-06 13:27 ` David Hildenbrand
2024-08-06 13:27 ` David Hildenbrand
2024-08-01 6:08 ` [PATCH v3 26/26] docs: move numa=fake description to kernel-parameters.txt Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-01 6:08 ` Mike Rapoport
2024-08-02 15:09 ` Jonathan Cameron
2024-08-02 15:09 ` Jonathan Cameron
2024-08-02 15:09 ` Jonathan Cameron
2024-08-06 13:25 ` David Hildenbrand
2024-08-06 13:25 ` David Hildenbrand
2024-08-06 13:25 ` David Hildenbrand
2024-08-02 16:44 ` [PATCH v3 00/26] mm: introduce numa_memblks Jonathan Cameron
2024-08-02 16:44 ` Jonathan Cameron
2024-08-02 16:44 ` Jonathan Cameron
2024-08-05 19:41 ` Dan Williams
2024-08-05 19:41 ` Dan Williams
2024-08-05 19:41 ` Dan Williams
2024-08-05 20:26 ` Dan Williams
2024-08-05 20:26 ` Dan Williams
2024-08-05 20:26 ` 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=20240802113629.00003069@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=andreas@gaisler.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=chenhuacai@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave@stgolabs.net \
--cc=davem@davemloft.net \
--cc=david@redhat.com \
--cc=devicetree@vger.kernel.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=gor@linux.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=hca@linux.ibm.com \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=loongarch@lists.linux.dev \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=nvdimm@lists.linux.dev \
--cc=palmer@dabbelt.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=rppt@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=sparclinux@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tsbogend@alpha.franken.de \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=ziy@nvidia.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.