From: "David Hildenbrand (Arm)" <david@kernel.org>
To: "linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
KVM <kvm@vger.kernel.org>
Cc: ackerleytng@google.com, amit@infradead.org,
aneeshkumar.kizhakeveetil@arm.com, ashish.kalra@amd.com,
dan.j.williams@intel.com, eberman@quicinc.com, fvdl@google.com,
gshan@redhat.com, jackmanb@google.com, jackyli@google.com,
jthoughton@google.com, kalyazin@amazon.com,
kevinloughlin@google.com, liruxin@google.com,
michael.day@amd.com, michael.roth@amd.com,
mike.rapoport@gmail.com, mvaralar@redhat.com,
pankaj.gupta@amd.com, papaluri@amd.com, patrick.roy@linux.dev,
Peter Xu <peterx@redhat.com>,
pheragu@quicinc.com, pkondeti@qti.qualcomm.com,
psalian@google.com, seanjc@google.com, shan.gavin@gmail.com,
shivankg@amd.com, sidtelang@google.com, suzuki.poulose@arm.com,
tabba@google.com, tatashin@google.com, vannapurve@google.com,
vbabka@suse.com, wyihan@google.com
Subject: [Invitation] bi-weekly guest_memfd upstream call on 2026-03-05
Date: Wed, 4 Mar 2026 21:11:16 +0100 [thread overview]
Message-ID: <2ae32797-03a8-4d05-b510-615ae0418b28@kernel.org> (raw)
Hi,
Our next guest_memfd upstream call is scheduled for tomorrow, Thursday,
2026-03-05 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 an google
calendar invitation that also covers all future meetings, just write me
or Ackerley a mail.
For some reason, google seems to randomly drop all invitees from the
calendar entry ... so expect some annoying invitation mails until that
seems to stop.
In this meeting, Ackerley will give us an update on guest_memfd HugeTLB
support, which we were not able to squeeze into the last meeting. I'm
sure, other things will pop up around HugeTLB support and
expected/desired timelines.
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
[2] https://lore.kernel.org/all/20251203144159.6131-1-itazur@amazon.com/
--
Cheers,
David
reply other threads:[~2026-03-04 20:11 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=2ae32797-03a8-4d05-b510-615ae0418b28@kernel.org \
--to=david@kernel.org \
--cc=ackerleytng@google.com \
--cc=amit@infradead.org \
--cc=aneeshkumar.kizhakeveetil@arm.com \
--cc=ashish.kalra@amd.com \
--cc=dan.j.williams@intel.com \
--cc=eberman@quicinc.com \
--cc=fvdl@google.com \
--cc=gshan@redhat.com \
--cc=jackmanb@google.com \
--cc=jackyli@google.com \
--cc=jthoughton@google.com \
--cc=kalyazin@amazon.com \
--cc=kevinloughlin@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-mm@kvack.org \
--cc=liruxin@google.com \
--cc=michael.day@amd.com \
--cc=michael.roth@amd.com \
--cc=mike.rapoport@gmail.com \
--cc=mvaralar@redhat.com \
--cc=pankaj.gupta@amd.com \
--cc=papaluri@amd.com \
--cc=patrick.roy@linux.dev \
--cc=peterx@redhat.com \
--cc=pheragu@quicinc.com \
--cc=pkondeti@qti.qualcomm.com \
--cc=psalian@google.com \
--cc=seanjc@google.com \
--cc=shan.gavin@gmail.com \
--cc=shivankg@amd.com \
--cc=sidtelang@google.com \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.com \
--cc=tatashin@google.com \
--cc=vannapurve@google.com \
--cc=vbabka@suse.com \
--cc=wyihan@google.com \
/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