From: David Hildenbrand via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Shivank Garg <shivankg@amd.com>,
willy@infradead.org, akpm@linux-foundation.org,
pbonzini@redhat.com, shuah@kernel.org, seanjc@google.com,
vbabka@suse.cz
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, linux-coco@lists.linux.dev,
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, jgg@nvidia.com
Subject: Re: [f2fs-dev] [PATCH kvm-next V11 0/7] Add NUMA mempolicy support for KVM guest-memfd
Date: Wed, 24 Sep 2025 20:19:00 +0200 [thread overview]
Message-ID: <1b01ebab-a43e-4344-ae38-50f0a031332f@redhat.com> (raw)
In-Reply-To: <20250827175247.83322-2-shivankg@amd.com>
On 27.08.25 19:52, 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)
>
Heads-up: I'll queue this (incl. the replacement patch for #4 from the
reply) and send it tomorrow as a PR against kvm/next to Paolo.
--
Cheers
David / dhildenb
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2025-09-24 18:19 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 17:52 [f2fs-dev] [PATCH kvm-next V11 0/7] Add NUMA mempolicy support for KVM guest-memfd Shivank Garg via Linux-f2fs-devel
2025-08-27 17:52 ` [f2fs-dev] [PATCH kvm-next V11 1/7] mm/filemap: Add NUMA mempolicy support to filemap_alloc_folio() Shivank Garg via Linux-f2fs-devel
2025-08-27 17:52 ` [f2fs-dev] [PATCH kvm-next V11 2/7] mm/filemap: Extend __filemap_get_folio() to support NUMA memory policies Shivank Garg via Linux-f2fs-devel
2025-08-27 17:52 ` [f2fs-dev] [PATCH kvm-next V11 3/7] mm/mempolicy: Export memory policy symbols Shivank Garg via Linux-f2fs-devel
2025-08-27 17:52 ` [f2fs-dev] [PATCH kvm-next V11 4/7] KVM: guest_memfd: Use guest mem inodes instead of anonymous inodes Shivank Garg via Linux-f2fs-devel
2025-08-27 22:43 ` Ackerley Tng via Linux-f2fs-devel
2025-08-28 5:49 ` Garg, Shivank via Linux-f2fs-devel
2025-08-28 10:06 ` David Hildenbrand via Linux-f2fs-devel
2025-09-25 2:50 ` Sean Christopherson via Linux-f2fs-devel
2025-09-25 11:44 ` Garg, Shivank via Linux-f2fs-devel
2025-09-25 11:55 ` David Hildenbrand via Linux-f2fs-devel
2025-09-25 13:41 ` Sean Christopherson via Linux-f2fs-devel
2025-09-25 13:44 ` Fuad Tabba via Linux-f2fs-devel
2025-09-25 14:26 ` David Hildenbrand via Linux-f2fs-devel
2025-09-25 15:06 ` Sean Christopherson via Linux-f2fs-devel
2025-08-27 17:52 ` [f2fs-dev] [PATCH kvm-next V11 5/7] KVM: guest_memfd: Add slab-allocated inode cache Shivank Garg via Linux-f2fs-devel
2025-09-25 14:05 ` Sean Christopherson via Linux-f2fs-devel
2025-09-25 14:17 ` Sean Christopherson via Linux-f2fs-devel
2025-08-27 17:52 ` [f2fs-dev] [PATCH kvm-next V11 6/7] KVM: guest_memfd: Enforce NUMA mempolicy using shared policy Shivank Garg via Linux-f2fs-devel
2025-09-25 14:22 ` Sean Christopherson via Linux-f2fs-devel
2025-09-26 19:36 ` Sean Christopherson via Linux-f2fs-devel
2025-10-15 21:45 ` Gregory Price
2025-10-15 22:48 ` Sean Christopherson via Linux-f2fs-devel
2025-10-16 12:58 ` Garg, Shivank via Linux-f2fs-devel
2025-10-16 14:17 ` Gregory Price
2025-08-27 17:52 ` [f2fs-dev] [PATCH kvm-next V11 7/7] KVM: guest_memfd: selftests: Add tests for mmap and NUMA policy support Shivank Garg via Linux-f2fs-devel
2025-09-25 21:35 ` Sean Christopherson via Linux-f2fs-devel
2025-09-25 23:03 ` Sean Christopherson via Linux-f2fs-devel
2025-09-25 23:04 ` Jason Gunthorpe via Linux-f2fs-devel
2025-09-25 23:12 ` Sean Christopherson via Linux-f2fs-devel
2025-09-26 7:32 ` David Hildenbrand via Linux-f2fs-devel
2025-09-26 7:31 ` David Hildenbrand via Linux-f2fs-devel
2025-09-26 7:37 ` Garg, Shivank via Linux-f2fs-devel
2025-08-28 12:44 ` [f2fs-dev] [PATCH kvm-next V11 0/7] Add NUMA mempolicy support for KVM guest-memfd David Hildenbrand via Linux-f2fs-devel
2025-09-24 18:19 ` David Hildenbrand via Linux-f2fs-devel [this message]
2025-09-24 20:35 ` Kalra, Ashish via Linux-f2fs-devel
2025-10-15 18:02 ` Sean Christopherson via Linux-f2fs-devel
2025-10-20 15:52 ` Sean Christopherson 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=1b01ebab-a43e-4344-ae38-50f0a031332f@redhat.com \
--to=linux-f2fs-devel@lists.sourceforge.net \
--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=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@nvidia.com \
--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-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=seanjc@google.com \
--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 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).