linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
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-10-31
Date: Tue, 29 Oct 2024 14:13:44 +0100	[thread overview]
Message-ID: <ae794891-fe69-411a-b82e-6963b594a62a@redhat.com> (raw)

Hi,

the next guest_memfd upstream call will happen this Thursday, 2024-10-31 
at at 9:00 - 10:00am (GMT-07: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.


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.

We'll continue our discussion on:
* Challenges with supporting huge pages
* Challenges with shared vs. private conversion (e.g., folio_put()
   callback)
* guest_memfd as a "library"

--

Current upstream proposals floating around:
* mmap support + shared vs. private [2]
* preparations [3] for huge/gigantic page support [4]
* guest_memfd as a "library" to make it independent of KVM [5]

[1] 
https://lkml.kernel.org/r/4b49248b-1cf1-44dc-9b50-ee551e1671ac@redhat.com
[2] https://lkml.kernel.org/r/20241010085930.1546800-1-tabba@google.com
[3] https://lkml.kernel.org/r/cover.1728684491.git.ackerleytng@google.com
[4] https://lkml.kernel.org/r/cover.1728684491.git.ackerleytng@google.com
[5] 
https://lkml.kernel.org/r/20240829-guest-memfd-lib-v2-0-b9afc1ff3656@quicinc.com

-- 
Cheers,

David / dhildenb



                 reply	other threads:[~2024-10-29 13:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=ae794891-fe69-411a-b82e-6963b594a62a@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