From: David Hildenbrand <david@redhat.com>
To: linux-coco@lists.linux.dev, KVM <kvm@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: [Invitation] bi-weekly guest_memfd upstream call on 2024-10-17
Date: Tue, 15 Oct 2024 12:55:01 +0200 [thread overview]
Message-ID: <df619e65-e65e-4856-b4ca-9938e8e08f18@redhat.com> (raw)
Hi,
as discussed [1], we'll get started with a bi-weekly guest_memfd
upstream call this Thursday, 2024-10-17 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
Current upstream proposals that we'll likely discuss to some degree (and that
might be reasonable to look at) are:
* 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]
There is a public calender entry [6] for the meeting, but Google might
only show it as "busy" although it is properly marked as "public". If
you want to a proper google calendar invitation that also covers all
future meetings, just write me a mail.
Cheers,
David
[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
[6] https://calendar.google.com/calendar/event?action=TEMPLATE&tmeid=YmNqb292ajc4b2gxbXZhdmdwODRob3E3MG9fMjAyNDEwMTdUMTYwMDAwWiBjXzcyMTNiN2RiYjY0OTc2YTgxZGNjODljYzIzYzZhZGY4MzExZjRjZWI5MTM0NWI2NTY1YzI2MTUwYzZiNGVjOWVAZw&tmsrc=c_7213b7dbb64976a81dcc89cc23c6adf8311f4ceb91345b6565c26150c6b4ec9e%40group.calendar.google.com&scp=ALL
--
Cheers,
David / dhildenb
reply other threads:[~2024-10-15 10:55 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=df619e65-e65e-4856-b4ca-9938e8e08f18@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).