From: "David Hildenbrand (Arm)" <david@kernel.org>
To: KVM <kvm@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>
Subject: bi-weekly guest_memfd upstream call on 2026-04-16
Date: Wed, 15 Apr 2026 21:18:51 +0200 [thread overview]
Message-ID: <dd0902ff-f132-4e07-96cd-2425af99ca55@kernel.org> (raw)
Hi all,
Our next guest_memfd upstream call is scheduled for tomorrow, Thursday,
2026-04-016 at 8:00 - 9:00am (GMT-07: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.
In this meeting, Mike wants to talk about IOMMU considerations for
in-place conversion/hugetlb with pass-through devices. And I'm sure
other things will pop up :)
To put something to discuss onto the agenda, reply to this mail or add
them to the meeting notes.
[1]
https://docs.google.com/document/d/1M6766BzdY1Lhk7LiR5IqVR8B8mG3cr-cxTxOrAosPOk/edit?usp=sharing
--
Cheers,
David
reply other threads:[~2026-04-15 19:19 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=dd0902ff-f132-4e07-96cd-2425af99ca55@kernel.org \
--to=david@kernel.org \
--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