linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
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>
Subject: [Invitation] bi-weekly guest_memfd upstream call on 2025-04-17
Date: Wed, 16 Apr 2025 13:58:20 +0200	[thread overview]
Message-ID: <971a3797-5fc4-4c7f-a856-dca05f9a874e@redhat.com> (raw)

Hi everybody,

our next guest_memfd upstream call is scheduled for Thursday,
2025-04-17 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
a mail.


If nothing else comes up, let's talk about the next steps to get basic 
mmap support [2] ready for upstream, to prepare for actual in-place 
conversion, direct-map removal and much more.

In particular, let's talk about what "basic mmap support" is, and what 
we can use it for without actual in-place conversion: IIUC "only shared 
memory in guest_memfd" use cases and some cases of software-protected 
VMs can use it.

Also, let's talk about the relationship/expectations between guest_memfd 
and the user (mmap) address when it comes to KVM memory slots that have 
a guest_memfd that supports "shared" memory.


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
[2] 
https://lore.kernel.org/all/20250318161823.4005529-1-tabba@google.com/T/#u

-- 
Cheers,

David / dhildenb



             reply	other threads:[~2025-04-16 11:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-16 11:58 David Hildenbrand [this message]
2025-04-16 13:20 ` Shivank Garg
2025-04-17  2:46 ` Chenyi Qiang
2025-04-17  7:14   ` 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=971a3797-5fc4-4c7f-a856-dca05f9a874e@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