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>
Cc: gshan@redhat.com, ackerleytng@google.com, kalyazin@amazon.com,
pankaj.gupta@amd.com, papaluri@amd.com, peterx@redhat.com,
seanjc@google.com, shivankg@amd.com, tabba@google.com,
vannapurve@google.com, shan.gavin@gmail.com,
aneeshkumar.kizhakeveetil@arm.com, ashish.kalra@amd.com,
dan.j.williams@intel.com, ddutile@redhat.com,
quic_eberman@quicinc.com, michael.roth@amd.com,
roypat@amazon.co.uk, suzuki.poulose@arm.com, vbabka@suse.com,
yuzhao@google.com, rppt@kernel.org, jgowans@amazon.com
Subject: [Invitation] bi-weekly guest_memfd upstream call on 2025-04-03
Date: Tue, 1 Apr 2025 20:46:36 +0200 [thread overview]
Message-ID: <7b3090fb-1816-4761-a7a5-17d49a050645@redhat.com> (raw)
Hi everybody,
our next guest_memfd upstream call is scheduled for Thursday,
2025-04-03 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
a mail.
In this meeting, I'll share some details from my LSF/MM session, and
we'll likely talk about the folio_put() callback and how to maybe limit
it to only specific cases (e.g., handing folios back to hugetlb after
truncate).
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
next reply other threads:[~2025-04-01 18:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 18:46 David Hildenbrand [this message]
2025-04-01 20:55 ` David Hildenbrand
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=7b3090fb-1816-4761-a7a5-17d49a050645@redhat.com \
--to=david@redhat.com \
--cc=ackerleytng@google.com \
--cc=aneeshkumar.kizhakeveetil@arm.com \
--cc=ashish.kalra@amd.com \
--cc=dan.j.williams@intel.com \
--cc=ddutile@redhat.com \
--cc=gshan@redhat.com \
--cc=jgowans@amazon.com \
--cc=kalyazin@amazon.com \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-mm@kvack.org \
--cc=michael.roth@amd.com \
--cc=pankaj.gupta@amd.com \
--cc=papaluri@amd.com \
--cc=peterx@redhat.com \
--cc=quic_eberman@quicinc.com \
--cc=roypat@amazon.co.uk \
--cc=rppt@kernel.org \
--cc=seanjc@google.com \
--cc=shan.gavin@gmail.com \
--cc=shivankg@amd.com \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.com \
--cc=vannapurve@google.com \
--cc=vbabka@suse.com \
--cc=yuzhao@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