From: David Hildenbrand <david@redhat.com>
To: "linux-coco@lists.linux.dev" <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 2025-02-06
Date: Wed, 5 Feb 2025 20:00:08 +0100 [thread overview]
Message-ID: <c980f0af-9f98-4bb9-9bfc-6ddd6af20fe9@redhat.com> (raw)
Hi everybody,
sorry for sending out this invitation late ... I was/am busy PTO'ing :)
Our next guest_memfd upstream call is scheduled for tomorrow, Thursday,
2025-02-06 at 8:00 - 9: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 can be found at [1], where we also link recordings and
collect current guest_memfd upstream proposals. If you want a google
calendar invitation that also covers all future meetings, just write me
a mail.
In this meeting, we'll continue the discussion we started last time:
* guest_memfd without "struct page" (i.e., no memmap at all,
or dynamically allocated memmap for "shared" pages only)
Further, we'll likely continue our discussion on:
* State of huge page support
* State of shared vs. private / mmap support
* State of shared device assignment support
* State of "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.
[1]
https://docs.google.com/document/d/1M6766BzdY1Lhk7LiR5IqVR8B8mG3cr-cxTxOrAosPOk/edit?usp=sharing
--
Cheers,
David / dhildenb
reply other threads:[~2025-02-05 19:00 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=c980f0af-9f98-4bb9-9bfc-6ddd6af20fe9@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