All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: willy@infradead.org, akpm@linux-foundation.org, david@redhat.com,
	 pbonzini@redhat.com, shuah@kernel.org, vbabka@suse.cz,
	 Shivank Garg <shivankg@amd.com>
Cc: brauner@kernel.org, viro@zeniv.linux.org.uk, dsterba@suse.com,
	 xiang@kernel.org, chao@kernel.org, jaegeuk@kernel.org,
	clm@fb.com,  josef@toxicpanda.com, kent.overstreet@linux.dev,
	zbestahu@gmail.com,  jefflexu@linux.alibaba.com,
	dhavale@google.com, lihongbo22@huawei.com,
	 lorenzo.stoakes@oracle.com, Liam.Howlett@oracle.com,
	rppt@kernel.org,  surenb@google.com, mhocko@suse.com,
	ziy@nvidia.com, matthew.brost@intel.com,
	 joshua.hahnjy@gmail.com, rakie.kim@sk.com, byungchul@sk.com,
	 gourry@gourry.net, ying.huang@linux.alibaba.com,
	apopple@nvidia.com,  tabba@google.com, ackerleytng@google.com,
	paul@paul-moore.com,  jmorris@namei.org, serge@hallyn.com,
	pvorel@suse.cz, bfoster@redhat.com,  vannapurve@google.com,
	chao.gao@intel.com, bharata@amd.com, nikunj@amd.com,
	 michael.day@amd.com, shdhiman@amd.com, yan.y.zhao@intel.com,
	 Neeraj.Upadhyay@amd.com, thomas.lendacky@amd.com,
	michael.roth@amd.com,  aik@amd.com, kalyazin@amazon.com,
	peterx@redhat.com, jack@suse.cz,  hch@infradead.org,
	cgzones@googlemail.com, ira.weiny@intel.com,
	 rientjes@google.com, roypat@amazon.co.uk, chao.p.peng@intel.com,
	 amit@infradead.org, ddutile@redhat.com,
	dan.j.williams@intel.com,  ashish.kalra@amd.com,
	gshan@redhat.com, jgowans@amazon.com,  pankaj.gupta@amd.com,
	papaluri@amd.com, yuzhao@google.com,  suzuki.poulose@arm.com,
	quic_eberman@quicinc.com,  linux-bcachefs@vger.kernel.org,
	linux-btrfs@vger.kernel.org,  linux-erofs@lists.ozlabs.org,
	linux-f2fs-devel@lists.sourceforge.net,
	 linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
	 linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org,  kvm@vger.kernel.org,
	linux-kselftest@vger.kernel.org,  linux-coco@lists.linux.dev,
	Jason Gunthorpe <jgg@ziepe.ca>
Subject: Re: [PATCH kvm-next V11 0/7] Add NUMA mempolicy support for KVM guest-memfd
Date: Mon, 20 Oct 2025 08:52:05 -0700	[thread overview]
Message-ID: <aPZapWWFGyqjA2e3@google.com> (raw)
In-Reply-To: <176055105546.1527431.3611256810380818215.b4-ty@google.com>

On Wed, Oct 15, 2025, Sean Christopherson wrote:
> On Wed, 27 Aug 2025 17:52:41 +0000, Shivank Garg wrote:
> > This series introduces NUMA-aware memory placement support for KVM guests
> > with guest_memfd memory backends. It builds upon Fuad Tabba's work (V17)
> > that enabled host-mapping for guest_memfd memory [1] and can be applied
> > directly applied on KVM tree [2] (branch kvm-next, base commit: a6ad5413,
> > Merge branch 'guest-memfd-mmap' into HEAD)
> > 
> > == Background ==
> > KVM's guest-memfd memory backend currently lacks support for NUMA policy
> > enforcement, causing guest memory allocations to be distributed across host
> > nodes  according to kernel's default behavior, irrespective of any policy
> > specified by the VMM. This limitation arises because conventional userspace
> > NUMA control mechanisms like mbind(2) don't work since the memory isn't
> > directly mapped to userspace when allocations occur.
> > Fuad's work [1] provides the necessary mmap capability, and this series
> > leverages it to enable mbind(2).
> > 
> > [...]
> 
> Applied the non-KVM change to kvm-x86 gmem.  We're still tweaking and iterating
> on the KVM changes, but I fully expect them to land in 6.19.
> 
> Holler if you object to taking these through the kvm tree.
> 
> [1/7] mm/filemap: Add NUMA mempolicy support to filemap_alloc_folio()
>       https://github.com/kvm-x86/linux/commit/601aa29f762f
> [2/7] mm/filemap: Extend __filemap_get_folio() to support NUMA memory policies
>       https://github.com/kvm-x86/linux/commit/2bb25703e5bd
> [3/7] mm/mempolicy: Export memory policy symbols
>       https://github.com/kvm-x86/linux/commit/e1b4cf7d6be3

FYI, I rebased these onto 6.18-rc2 to avoid a silly merge.  New hashes:

[1/3] mm/filemap: Add NUMA mempolicy support to filemap_alloc_folio()
      https://github.com/kvm-x86/linux/commit/7f3779a3ac3e
[2/3] mm/filemap: Extend __filemap_get_folio() to support NUMA memory policies
      https://github.com/kvm-x86/linux/commit/16a542e22339
[3/3] mm/mempolicy: Export memory policy symbols
      https://github.com/kvm-x86/linux/commit/f634f10809ec

WARNING: multiple messages have this Message-ID (diff)
From: Sean Christopherson via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: willy@infradead.org, akpm@linux-foundation.org, david@redhat.com,
	 pbonzini@redhat.com, shuah@kernel.org, vbabka@suse.cz,
	 Shivank Garg <shivankg@amd.com>
Cc: jgowans@amazon.com, mhocko@suse.com, jack@suse.cz,
	kvm@vger.kernel.org, dhavale@google.com,
	linux-btrfs@vger.kernel.org, aik@amd.com, papaluri@amd.com,
	kalyazin@amazon.com, peterx@redhat.com, linux-mm@kvack.org,
	clm@fb.com, ddutile@redhat.com, linux-kselftest@vger.kernel.org,
	shdhiman@amd.com, gshan@redhat.com, ying.huang@linux.alibaba.com,
	ira.weiny@intel.com, roypat@amazon.co.uk,
	matthew.brost@intel.com, Jason Gunthorpe <jgg@ziepe.ca>,
	zbestahu@gmail.com, lorenzo.stoakes@oracle.com,
	linux-bcachefs@vger.kernel.org, apopple@nvidia.com,
	jmorris@namei.org, hch@infradead.org, chao.gao@intel.com,
	cgzones@googlemail.com, ziy@nvidia.com, rientjes@google.com,
	yuzhao@google.com, xiang@kernel.org, nikunj@amd.com,
	gourry@gourry.net, serge@hallyn.com, amit@infradead.org,
	thomas.lendacky@amd.com, ashish.kalra@amd.com,
	chao.p.peng@intel.com, yan.y.zhao@intel.com, byungchul@sk.com,
	michael.day@amd.com, Neeraj.Upadhyay@amd.com,
	michael.roth@amd.com, bfoster@redhat.com, bharata@amd.com,
	josef@toxicpanda.com, Liam.Howlett@oracle.com,
	ackerleytng@google.com, dsterba@suse.com,
	viro@zeniv.linux.org.uk, jefflexu@linux.alibaba.com,
	jaegeuk@kernel.org, dan.j.williams@intel.com, surenb@google.com,
	tabba@google.com, paul@paul-moore.com, joshua.hahnjy@gmail.com,
	brauner@kernel.org, quic_eberman@quicinc.com, rakie.kim@sk.com,
	pvorel@suse.cz, linux-erofs@lists.ozlabs.org,
	kent.overstreet@linux.dev, linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net, pankaj.gupta@amd.com,
	linux-security-module@vger.kernel.org, lihongbo22@huawei.com,
	linux-fsdevel@vger.kernel.org, vannapurve@google.com,
	suzuki.poulose@arm.com, rppt@kernel.org,
	linux-coco@lists.linux.dev
Subject: Re: [f2fs-dev] [PATCH kvm-next V11 0/7] Add NUMA mempolicy support for KVM guest-memfd
Date: Mon, 20 Oct 2025 08:52:05 -0700	[thread overview]
Message-ID: <aPZapWWFGyqjA2e3@google.com> (raw)
In-Reply-To: <176055105546.1527431.3611256810380818215.b4-ty@google.com>

On Wed, Oct 15, 2025, Sean Christopherson wrote:
> On Wed, 27 Aug 2025 17:52:41 +0000, Shivank Garg wrote:
> > This series introduces NUMA-aware memory placement support for KVM guests
> > with guest_memfd memory backends. It builds upon Fuad Tabba's work (V17)
> > that enabled host-mapping for guest_memfd memory [1] and can be applied
> > directly applied on KVM tree [2] (branch kvm-next, base commit: a6ad5413,
> > Merge branch 'guest-memfd-mmap' into HEAD)
> > 
> > == Background ==
> > KVM's guest-memfd memory backend currently lacks support for NUMA policy
> > enforcement, causing guest memory allocations to be distributed across host
> > nodes  according to kernel's default behavior, irrespective of any policy
> > specified by the VMM. This limitation arises because conventional userspace
> > NUMA control mechanisms like mbind(2) don't work since the memory isn't
> > directly mapped to userspace when allocations occur.
> > Fuad's work [1] provides the necessary mmap capability, and this series
> > leverages it to enable mbind(2).
> > 
> > [...]
> 
> Applied the non-KVM change to kvm-x86 gmem.  We're still tweaking and iterating
> on the KVM changes, but I fully expect them to land in 6.19.
> 
> Holler if you object to taking these through the kvm tree.
> 
> [1/7] mm/filemap: Add NUMA mempolicy support to filemap_alloc_folio()
>       https://github.com/kvm-x86/linux/commit/601aa29f762f
> [2/7] mm/filemap: Extend __filemap_get_folio() to support NUMA memory policies
>       https://github.com/kvm-x86/linux/commit/2bb25703e5bd
> [3/7] mm/mempolicy: Export memory policy symbols
>       https://github.com/kvm-x86/linux/commit/e1b4cf7d6be3

FYI, I rebased these onto 6.18-rc2 to avoid a silly merge.  New hashes:

[1/3] mm/filemap: Add NUMA mempolicy support to filemap_alloc_folio()
      https://github.com/kvm-x86/linux/commit/7f3779a3ac3e
[2/3] mm/filemap: Extend __filemap_get_folio() to support NUMA memory policies
      https://github.com/kvm-x86/linux/commit/16a542e22339
[3/3] mm/mempolicy: Export memory policy symbols
      https://github.com/kvm-x86/linux/commit/f634f10809ec


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2025-10-20 15:52 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-27 17:52 [PATCH kvm-next V11 0/7] Add NUMA mempolicy support for KVM guest-memfd Shivank Garg
2025-08-27 17:52 ` [f2fs-dev] " Shivank Garg via Linux-f2fs-devel
2025-08-27 17:52 ` [PATCH kvm-next V11 1/7] mm/filemap: Add NUMA mempolicy support to filemap_alloc_folio() Shivank Garg
2025-08-27 17:52   ` [f2fs-dev] " Shivank Garg via Linux-f2fs-devel
2025-08-27 17:52 ` [PATCH kvm-next V11 2/7] mm/filemap: Extend __filemap_get_folio() to support NUMA memory policies Shivank Garg
2025-08-27 17:52   ` [f2fs-dev] " Shivank Garg via Linux-f2fs-devel
2025-08-27 17:52 ` [PATCH kvm-next V11 3/7] mm/mempolicy: Export memory policy symbols Shivank Garg
2025-08-27 17:52   ` [f2fs-dev] " Shivank Garg via Linux-f2fs-devel
2025-08-27 17:52 ` [PATCH kvm-next V11 4/7] KVM: guest_memfd: Use guest mem inodes instead of anonymous inodes Shivank Garg
2025-08-27 17:52   ` [f2fs-dev] " Shivank Garg via Linux-f2fs-devel
2025-08-27 22:43   ` Ackerley Tng
2025-08-27 22:43     ` [f2fs-dev] " Ackerley Tng via Linux-f2fs-devel
2025-08-28  5:49     ` Garg, Shivank
2025-08-28  5:49       ` [f2fs-dev] " Garg, Shivank via Linux-f2fs-devel
2025-08-28 10:06     ` David Hildenbrand
2025-08-28 10:06       ` [f2fs-dev] " David Hildenbrand via Linux-f2fs-devel
2025-09-25  2:50     ` Sean Christopherson
2025-09-25  2:50       ` [f2fs-dev] " Sean Christopherson via Linux-f2fs-devel
2025-09-25 11:44       ` Garg, Shivank
2025-09-25 11:44         ` [f2fs-dev] " Garg, Shivank via Linux-f2fs-devel
2025-09-25 11:55         ` David Hildenbrand
2025-09-25 11:55           ` [f2fs-dev] " David Hildenbrand via Linux-f2fs-devel
2025-09-25 13:41           ` Sean Christopherson
2025-09-25 13:41             ` [f2fs-dev] " Sean Christopherson via Linux-f2fs-devel
2025-09-25 13:44             ` Fuad Tabba
2025-09-25 13:44               ` [f2fs-dev] " Fuad Tabba via Linux-f2fs-devel
2025-09-25 14:26             ` David Hildenbrand
2025-09-25 14:26               ` [f2fs-dev] " David Hildenbrand via Linux-f2fs-devel
2025-09-25 15:06               ` Sean Christopherson
2025-09-25 15:06                 ` [f2fs-dev] " Sean Christopherson via Linux-f2fs-devel
2025-09-25 23:11                 ` Sean Christopherson
2025-09-26  6:20                   ` Garg, Shivank
2025-08-27 17:52 ` [PATCH kvm-next V11 5/7] KVM: guest_memfd: Add slab-allocated inode cache Shivank Garg
2025-08-27 17:52   ` [f2fs-dev] " Shivank Garg via Linux-f2fs-devel
2025-09-25 14:05   ` Sean Christopherson
2025-09-25 14:05     ` [f2fs-dev] " Sean Christopherson via Linux-f2fs-devel
2025-09-25 14:17     ` Sean Christopherson
2025-09-25 14:17       ` [f2fs-dev] " Sean Christopherson via Linux-f2fs-devel
2025-08-27 17:52 ` [PATCH kvm-next V11 6/7] KVM: guest_memfd: Enforce NUMA mempolicy using shared policy Shivank Garg
2025-08-27 17:52   ` [f2fs-dev] " Shivank Garg via Linux-f2fs-devel
2025-09-25 14:22   ` Sean Christopherson
2025-09-25 14:22     ` [f2fs-dev] " Sean Christopherson via Linux-f2fs-devel
2025-09-26 19:36     ` Sean Christopherson
2025-09-26 19:36       ` [f2fs-dev] " Sean Christopherson via Linux-f2fs-devel
2025-10-15 21:45       ` Gregory Price
2025-10-15 21:45         ` Gregory Price
2025-10-15 22:48         ` Sean Christopherson
2025-10-15 22:48           ` Sean Christopherson via Linux-f2fs-devel
2025-10-16 12:58           ` Garg, Shivank
2025-10-16 12:58             ` Garg, Shivank via Linux-f2fs-devel
2025-10-16 14:17           ` Gregory Price
2025-10-16 14:17             ` Gregory Price
2025-08-27 17:52 ` [PATCH kvm-next V11 7/7] KVM: guest_memfd: selftests: Add tests for mmap and NUMA policy support Shivank Garg
2025-08-27 17:52   ` [f2fs-dev] " Shivank Garg via Linux-f2fs-devel
2025-09-25 21:35   ` Sean Christopherson
2025-09-25 21:35     ` [f2fs-dev] " Sean Christopherson via Linux-f2fs-devel
2025-09-25 23:03     ` Sean Christopherson
2025-09-25 23:03       ` [f2fs-dev] " Sean Christopherson via Linux-f2fs-devel
2025-09-25 23:04     ` Jason Gunthorpe
2025-09-25 23:04       ` [f2fs-dev] " Jason Gunthorpe via Linux-f2fs-devel
2025-09-25 23:12       ` Sean Christopherson
2025-09-25 23:12         ` [f2fs-dev] " Sean Christopherson via Linux-f2fs-devel
2025-09-26  7:32       ` David Hildenbrand
2025-09-26  7:32         ` [f2fs-dev] " David Hildenbrand via Linux-f2fs-devel
2025-09-26  7:31     ` David Hildenbrand
2025-09-26  7:31       ` [f2fs-dev] " David Hildenbrand via Linux-f2fs-devel
2025-09-26  7:37       ` Garg, Shivank
2025-09-26  7:37         ` [f2fs-dev] " Garg, Shivank via Linux-f2fs-devel
2025-08-28 12:44 ` [PATCH kvm-next V11 0/7] Add NUMA mempolicy support for KVM guest-memfd David Hildenbrand
2025-08-28 12:44   ` [f2fs-dev] " David Hildenbrand via Linux-f2fs-devel
2025-09-24 18:19 ` David Hildenbrand
2025-09-24 18:19   ` [f2fs-dev] " David Hildenbrand via Linux-f2fs-devel
2025-09-24 20:35   ` Kalra, Ashish
2025-09-24 20:35     ` [f2fs-dev] " Kalra, Ashish via Linux-f2fs-devel
2025-10-15 18:02 ` Sean Christopherson
2025-10-15 18:02   ` [f2fs-dev] " Sean Christopherson via Linux-f2fs-devel
2025-10-20 15:52   ` Sean Christopherson [this message]
2025-10-20 15:52     ` Sean Christopherson via Linux-f2fs-devel
2025-12-09 17:18 ` patchwork-bot+f2fs
2025-12-09 17:18   ` patchwork-bot+f2fs--- via Linux-f2fs-devel

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=aPZapWWFGyqjA2e3@google.com \
    --to=seanjc@google.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=Neeraj.Upadhyay@amd.com \
    --cc=ackerleytng@google.com \
    --cc=aik@amd.com \
    --cc=akpm@linux-foundation.org \
    --cc=amit@infradead.org \
    --cc=apopple@nvidia.com \
    --cc=ashish.kalra@amd.com \
    --cc=bfoster@redhat.com \
    --cc=bharata@amd.com \
    --cc=brauner@kernel.org \
    --cc=byungchul@sk.com \
    --cc=cgzones@googlemail.com \
    --cc=chao.gao@intel.com \
    --cc=chao.p.peng@intel.com \
    --cc=chao@kernel.org \
    --cc=clm@fb.com \
    --cc=dan.j.williams@intel.com \
    --cc=david@redhat.com \
    --cc=ddutile@redhat.com \
    --cc=dhavale@google.com \
    --cc=dsterba@suse.com \
    --cc=gourry@gourry.net \
    --cc=gshan@redhat.com \
    --cc=hch@infradead.org \
    --cc=ira.weiny@intel.com \
    --cc=jack@suse.cz \
    --cc=jaegeuk@kernel.org \
    --cc=jefflexu@linux.alibaba.com \
    --cc=jgg@ziepe.ca \
    --cc=jgowans@amazon.com \
    --cc=jmorris@namei.org \
    --cc=josef@toxicpanda.com \
    --cc=joshua.hahnjy@gmail.com \
    --cc=kalyazin@amazon.com \
    --cc=kent.overstreet@linux.dev \
    --cc=kvm@vger.kernel.org \
    --cc=lihongbo22@huawei.com \
    --cc=linux-bcachefs@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-coco@lists.linux.dev \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=matthew.brost@intel.com \
    --cc=mhocko@suse.com \
    --cc=michael.day@amd.com \
    --cc=michael.roth@amd.com \
    --cc=nikunj@amd.com \
    --cc=pankaj.gupta@amd.com \
    --cc=papaluri@amd.com \
    --cc=paul@paul-moore.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=pvorel@suse.cz \
    --cc=quic_eberman@quicinc.com \
    --cc=rakie.kim@sk.com \
    --cc=rientjes@google.com \
    --cc=roypat@amazon.co.uk \
    --cc=rppt@kernel.org \
    --cc=serge@hallyn.com \
    --cc=shdhiman@amd.com \
    --cc=shivankg@amd.com \
    --cc=shuah@kernel.org \
    --cc=surenb@google.com \
    --cc=suzuki.poulose@arm.com \
    --cc=tabba@google.com \
    --cc=thomas.lendacky@amd.com \
    --cc=vannapurve@google.com \
    --cc=vbabka@suse.cz \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.org \
    --cc=xiang@kernel.org \
    --cc=yan.y.zhao@intel.com \
    --cc=ying.huang@linux.alibaba.com \
    --cc=yuzhao@google.com \
    --cc=zbestahu@gmail.com \
    --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.