From: David Hildenbrand <david@redhat.com>
To: linux-coco@lists.linux.dev,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
KVM <kvm@vger.kernel.org>
Subject: [Invitation] bi-weekly guest_memfd upstream call on 2024-11-14
Date: Tue, 12 Nov 2024 13:30:06 +0100 [thread overview]
Message-ID: <6f2bfac2-d9e7-4e4a-9298-7accded16b4f@redhat.com> (raw)
Hi,
the next guest_memfd upstream call will happen this Thursday, 2024-11-14
at at 9:00 - 10:00am (GMT-08:00) Pacific Time - Vancouver.
We'll be using the following Google meet:
http://meet.google.com/wxp-wtju-jzw
The meeting notes are linked from the google calendar invitation. If you
want an invitation that also covers all future meetings, just write me a
mail.
In this meeting we'll discuss:
* fbind() and NUMA mempolicy for guest_memfd
* Persisting guest_memfd across reboot / guest_memfs
* guest_memfd use cases for a PFN range allocator
And we'll continue our discussion on:
* Challenges with supporting huge pages
* Challenges with shared vs. private conversion
* guest_memfd as a "library"
To put something to discuss onto the agenda, reply to this mail or add
them to the "Topics/questions for next meeting(s)" section in the
meeting notes as a comment.
--
Current upstream proposals floating around:
* mmap support + shared vs. private [1]
* preparations [2] for huge/gigantic page support [3]
* guest_memfd as a "library" to make it independent of KVM [4]
* fbind() and NUMA mempolicy for guest_memfd [5]
* Hooking into folio_put() [6]
[1] https://lkml.kernel.org/r/20241010085930.1546800-1-tabba@google.com
[2] https://lkml.kernel.org/r/cover.1728684491.git.ackerleytng@google.com
[3] https://lkml.kernel.org/r/cover.1728684491.git.ackerleytng@google.com
[4]
https://lkml.kernel.org/r/20240829-guest-memfd-lib-v2-0-b9afc1ff3656@quicinc.com
[5]
https://lore.kernel.org/all/20241105164549.154700-1-shivankg@amd.com/T/#u
[6] https://lkml.kernel.org/r/20241108162040.159038-1-tabba@google.com
--
Cheers,
David / dhildenb
next reply other threads:[~2024-11-12 12:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 12:30 David Hildenbrand [this message]
2024-11-13 6:06 ` [Invitation] bi-weekly guest_memfd upstream call on 2024-11-14 Chao Gao
2024-11-13 15:04 ` David Hildenbrand
2024-11-14 2:27 ` Chao Gao
2024-12-24 4:21 ` Alexey Kardashevskiy
2024-12-24 11:27 ` David Hildenbrand
2024-12-27 4:21 ` Alexey Kardashevskiy
2024-11-27 16:43 ` [Invitation] bi-weekly guest_memfd upstream call on 2024-12-05 David Hildenbrand
2024-12-10 14:25 ` [Invitation] bi-weekly guest_memfd upstream call on 2024-12-12 David Hildenbrand
2024-12-11 13:53 ` Gowans, James
2025-01-08 10:45 ` [Invitation] bi-weekly guest_memfd upstream call on 2025-01-09 David Hildenbrand
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=6f2bfac2-d9e7-4e4a-9298-7accded16b4f@redhat.com \
--to=david@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-mm@kvack.org \
/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).