From: Gavin Shan <gshan@redhat.com>
To: David Hildenbrand <david@redhat.com>,
linux-coco@lists.linux.dev, KVM <kvm@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: Proposal: bi-weekly guest_memfd upstream call
Date: Wed, 16 Oct 2024 20:58:46 +1000 [thread overview]
Message-ID: <7e4febb3-1fab-4c2d-8c85-b25fa3c94765@redhat.com> (raw)
In-Reply-To: <4b49248b-1cf1-44dc-9b50-ee551e1671ac@redhat.com>
Hi David,
On 10/10/24 11:39 PM, David Hildenbrand wrote:
> Ahoihoi,
>
> while talking to a bunch of folks at LPC about guest_memfd, it was raised that there isn't really a place for people to discuss the development of guest_memfd on a regular basis.
>
> There is a KVM upstream call, but guest_memfd is on its way of not being guest_memfd specific ("library") and there is the bi-weekly MM alignment call, but we're not going to hijack that meeting completely + a lot of guest_memfd stuff doesn't need all the MM experts ;)
>
> So my proposal would be to have a bi-weekly meeting, to discuss ongoing development of guest_memfd, in particular:
>
> (1) Organize development: (do we need 3 different implementation
> of mmap() support ? ;) )
> (2) Discuss current progress and challenges
> (3) Cover future ideas and directions
> (4) Whatever else makes sense
>
> Topic-wise it's relatively clear: guest_memfd extensions were one of the hot topics at LPC ;)
>
> I would suggest every second Thursdays from 9:00 - 10:00am PDT (GMT-7), starting Thursday next week (2024-10-17).
>
> We would be using Google Meet.
>
>
> Thoughts?
>
Thanks for organizing it. I'm intrested and please include me if there
is a invite.
Thanks,
Gavin
next prev parent reply other threads:[~2024-10-16 10:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 13:39 Proposal: bi-weekly guest_memfd upstream call David Hildenbrand
2024-10-10 14:20 ` Vishal Annapurve
2024-10-11 20:01 ` Michael Roth
2024-10-10 14:30 ` Fuad Tabba
2024-10-10 14:38 ` David Hildenbrand
2024-10-10 17:14 ` Ackerley Tng
2024-10-11 11:50 ` David Hildenbrand
2024-10-11 15:15 ` Sean Christopherson
2024-10-11 17:48 ` Ackerley Tng
2024-10-14 9:05 ` Vlastimil Babka
2024-10-14 9:34 ` David Hildenbrand
2024-10-11 17:57 ` Dan Williams
2024-10-12 3:58 ` Gupta, Pankaj
2024-10-15 10:24 ` Patrick Roy
2024-10-16 9:31 ` Suzuki K Poulose
2024-10-16 10:58 ` Gavin Shan [this message]
2024-10-21 8:05 ` Kalra, Ashish
2024-11-04 20:36 ` Ackerley Tng
2024-11-14 16:29 ` David Hildenbrand
2024-11-15 13:18 ` Amit Shah
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=7e4febb3-1fab-4c2d-8c85-b25fa3c94765@redhat.com \
--to=gshan@redhat.com \
--cc=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).