Re: [PATCH v13] mm: report per-page metadata information

2024-08-05 Thread Alison Schofield
On Mon, Aug 05, 2024 at 02:40:48PM -0400, Pasha Tatashin wrote: > On Fri, Aug 2, 2024 at 3:02 PM Alison Schofield > wrote: > > > > ++ nvdimm, linux-cxl, Yu Zhang > > > > On Wed, Jun 05, 2024 at 10:27:51PM +, Sourav Panda wrote: > > > Today, we do not have any observability of per-page metadata

Re: [PATCH v13] mm: report per-page metadata information

2024-08-05 Thread Dan Williams
Pasha Tatashin wrote: [..] > Thank you for the heads up. Can you please attach a full config file, > also was anyone able to reproduce this problem in qemu with emulated > nvdimm? Yes, I can reproduce the crash just by trying to reconfigure the mode of a pmem namespace: # ndctl create-namespace -

Re: [PATCH v3 11/26] x86/numa: use get_pfn_range_for_nid to verify that node spans memory

2024-08-05 Thread Mike Rapoport
On Mon, Aug 05, 2024 at 01:03:56PM -0700, Dan Williams wrote: > Mike Rapoport wrote: > > From: "Mike Rapoport (Microsoft)" > > > > 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 l

Re: [PATCH v3 22/26] mm: numa_memblks: use memblock_{start,end}_of_DRAM() when sanitizing meminfo

2024-08-05 Thread Mike Rapoport
On Mon, Aug 05, 2024 at 01:21:02PM -0700, Dan Williams wrote: > Mike Rapoport wrote: > > From: "Mike Rapoport (Microsoft)" > > > > numa_cleanup_meminfo() moves blocks outside system RAM to > > numa_reserved_meminfo and it uses 0 and PFN_PHYS(max_pfn) to determine > > the memory boundaries. > > >

Re: [PATCH v3 00/26] mm: introduce numa_memblks

2024-08-05 Thread Dan Williams
Dan Williams wrote: > Mike Rapoport wrote: > > From: "Mike Rapoport (Microsoft)" > > > > Hi, > > > > Following the discussion about handling of CXL fixed memory windows on > > arm64 [1] I decided to bite the bullet and move numa_memblks from x86 to > > the generic code so they will be available

Re: [PATCH v3 25/26] mm: make range-to-target_node lookup facility a part of numa_memblks

2024-08-05 Thread Dan Williams
Mike Rapoport wrote: > From: "Mike Rapoport (Microsoft)" > > The x86 implementation of range-to-target_node lookup (i.e. > phys_to_target_node() and memory_add_physaddr_to_nid()) relies on > numa_memblks. > > Since numa_memblks are now part of the generic code, move these > functions from x86 to

Re: [PATCH v3 22/26] mm: numa_memblks: use memblock_{start,end}_of_DRAM() when sanitizing meminfo

2024-08-05 Thread Dan Williams
Mike Rapoport wrote: > From: "Mike Rapoport (Microsoft)" > > numa_cleanup_meminfo() moves blocks outside system RAM to > numa_reserved_meminfo and it uses 0 and PFN_PHYS(max_pfn) to determine > the memory boundaries. > > Replace the memory range boundaries with more portable > memblock_start_of_

Re: [PATCH v3 19/26] mm: introduce numa_emulation

2024-08-05 Thread Dan Williams
Mike Rapoport wrote: > From: "Mike Rapoport (Microsoft)" > > Move numa_emulation codfrom arch/x86 to mm/numa_emulation.c s/codfrom/code from/ I am surprised that numa-emulation stayed x86 only for so long. I think it is useful facility for debugging NUMA scaling and heterogenous memory topologi

Re: [PATCH v3 11/26] x86/numa: use get_pfn_range_for_nid to verify that node spans memory

2024-08-05 Thread Dan Williams
Mike Rapoport wrote: > From: "Mike Rapoport (Microsoft)" > > 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 (Microso

Re: [PATCH v3 00/26] mm: introduce numa_memblks

2024-08-05 Thread Dan Williams
Mike Rapoport wrote: > From: "Mike Rapoport (Microsoft)" > > Hi, > > Following the discussion about handling of CXL fixed memory windows on > arm64 [1] I decided to bite the bullet and move numa_memblks from x86 to > the generic code so they will be available on arm64/riscv and maybe on > loonga

Re: [PATCH v13] mm: report per-page metadata information

2024-08-05 Thread Pasha Tatashin
On Fri, Aug 2, 2024 at 3:02 PM Alison Schofield wrote: > > ++ nvdimm, linux-cxl, Yu Zhang > > On Wed, Jun 05, 2024 at 10:27:51PM +, Sourav Panda wrote: > > Today, we do not have any observability of per-page metadata > > and how much it takes away from the machine capacity. Thus, > > we want t

Re: [PATCH v3 09/26] arch, mm: pull out allocation of NODE_DATA to generic code

2024-08-05 Thread Mike Rapoport
On Fri, Aug 02, 2024 at 10:55:27AM +0100, Jonathan Cameron wrote: > On Thu, 1 Aug 2024 09:08:09 +0300 > Mike Rapoport wrote: > > > From: "Mike Rapoport (Microsoft)" > > > > Architectures that support NUMA duplicate the code that allocates > > NODE_DATA on the node-local memory with slight vari

Re: [PATCH v3 07/26] mm: drop CONFIG_HAVE_ARCH_NODEDATA_EXTENSION

2024-08-05 Thread Mike Rapoport
On Sun, Aug 04, 2024 at 04:11:19PM +0100, Jonathan Cameron wrote: > On Sun, 4 Aug 2024 10:24:15 +0300 > Mike Rapoport wrote: > > > On Sat, Aug 03, 2024 at 11:58:13AM -0700, Andrew Morton wrote: > > > On Fri, 2 Aug 2024 10:49:22 +0100 Jonathan Cameron > > > wrote: > > > > > > > > --- a/mm/mm_

Re: [PATCH 01/18] KVM: x86: hyper-v: Introduce XMM output support

2024-08-05 Thread Nicolas Saenz Julienne
On Mon Jul 29, 2024 at 1:53 PM UTC, Vitaly Kuznetsov wrote: > CAUTION: This email originated from outside of the organization. Do not click > links or open attachments unless you can confirm the sender and know the > content is safe. > Nicolas Saenz Julienne writes: > > > Hi Vitaly, > > Thanks f