linux-coco.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: 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 2025-01-09
Date: Wed, 8 Jan 2025 11:45:21 +0100	[thread overview]
Message-ID: <0733555b-886e-42c4-ac06-fbd0a324e186@redhat.com> (raw)
In-Reply-To: <b9567cbf-8ad7-440a-8768-f4e7dbd2b5f7@redhat.com>

Hi everybody,

Happy New Year! I just returned from PTO, so I'm a bit late with the 
invitation ...

We'll have our next guest_memfd upstream call tomorrow,  Thursday, 
2025-01-09 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.

We don't have a lot yet on the agenda, so maybe this meeting will be 
less packed? :)

In this meeting we'll likely talk about:
  * Fuad's updated "restricted mapping" series from 2024-12-13. Hopefully
    Fuad can give us an overview :)
  * Michael's 2MN THP series (although Michael will likely not be around)

And we'll continue our discussion on:
  * Challenges with supporting huge pages
  * Challenges with shared vs. private conversion
  * guest_memfd as a "library"

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


      parent reply	other threads:[~2025-01-08 10:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-12 12:30 [Invitation] bi-weekly guest_memfd upstream call on 2024-11-14 David Hildenbrand
2024-11-13  6:06 ` Chao Gao
2024-11-13 15:04   ` David Hildenbrand
2024-11-14  2:27     ` Chao Gao
2024-12-24  4:21       ` Alexey Kardashevskiy
2024-12-24 11:27         ` David Hildenbrand
2024-12-27  4:21           ` Alexey Kardashevskiy
2024-11-27 16:43 ` [Invitation] bi-weekly guest_memfd upstream call on 2024-12-05 David Hildenbrand
2024-12-10 14:25   ` [Invitation] bi-weekly guest_memfd upstream call on 2024-12-12 David Hildenbrand
2024-12-11 13:53     ` Gowans, James
2025-01-08 10:45     ` David Hildenbrand [this message]

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=0733555b-886e-42c4-ac06-fbd0a324e186@redhat.com \
    --to=david@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).