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>
Subject: [Invitation] bi-weekly guest_memfd upstream call on 2026-08-19
Date: Wed, 19 Aug 2026 18:23:09 +0200 [thread overview]
Message-ID: <54d375aa-8362-4e1c-8f76-bae1eb9f4f76@kernel.org> (raw)
Hi,
Our next guest_memfd upstream call is scheduled for tomorrow, Thursday,
2026-08-19 8:00 - 9:00am (GMT-07:00) Pacific Time - Vancouver.
Note that we will be skipping the meeting in two weeks (2026-09-03) as both
Ackerley and me will be traveling. So if you have something urgent to discuss,
please speak up :)
In this meeting, I think we should sync on the recent developemnts regarding
in-place conversion. I don't know whether David Woodhouse will make this
meeting, but if so, we will also talk about guest_memfd+VFIO.
So this meeting could either be extremely short or very long :)
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.
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
next reply other threads:[~2026-08-19 16:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 16:23 David Hildenbrand (Arm) [this message]
2026-08-19 17:03 ` [Invitation] bi-weekly guest_memfd upstream call on 2026-08-19 David Woodhouse
2026-08-19 20:11 ` David Hildenbrand (Arm)
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=54d375aa-8362-4e1c-8f76-bae1eb9f4f76@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