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,
dwmw2@infradead.org, eberman@quicinc.com, fvdl@google.com,
gshan@redhat.com, jackmanb@google.com, jackyli@google.com,
jthoughton@google.com, kalyazin@amazon.com, kas@kernel.org,
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, prty@google.com,
psalian@google.com, qinkun@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-10-01
Date: Wed, 30 Sep 2026 18:57:22 +0200 [thread overview]
Message-ID: <471526fa-b31c-48a1-a602-208bb8113b7f@kernel.org> (raw)
Hi,
Our next guest_memfd upstream call is scheduled for tomorrow, Thursday,
2026-10-01 8:00 - 9:00am (GMT-07:00) Pacific Time - Vancouver.
Now that in-place conversion is on its way upstream, we can organize next steps.
With that in mind, it would be a good to talk about Ackerley's proposal [2] on
how to make guest_memfd obtain memory from other memory pools, not just the buddy.
We'll be using the following Google meet:
http://meet.google.com/wxp-wtju-jzw
The meeting notes can be found at [2], 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.
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://lore.kernel.org/r/20260925-gmem-tmpfs-backend-v1-0-d36159822d18@google.com
[2]
https://docs.google.com/document/d/1M6766BzdY1Lhk7LiR5IqVR8B8mG3cr-cxTxOrAosPOk/edit?usp=sharing
--
Cheers,
David
reply other threads:[~2026-09-30 16:57 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=471526fa-b31c-48a1-a602-208bb8113b7f@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=dwmw2@infradead.org \
--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=kas@kernel.org \
--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=prty@google.com \
--cc=psalian@google.com \
--cc=qinkun@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