From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>,
James Houghton <jthoughton@google.com>,
Peter Xu <peterx@redhat.com>,
Axel Rasmussen <axelrasmussen@google.com>,
Oliver Upton <oliver.upton@linux.dev>,
David Matlack <dmatlack@google.com>,
Aaron Lewis <aaronlewis@google.com>,
Isaku Yamahata <isaku.yamahata@linux.intel.com>,
Yan Zhao <yan.y.zhao@intel.com>, Marc Zyngier <maz@kernel.org>
Subject: [ANNOUNCE] PUCK Notes - 2024.01.03 - Post-copy for guest_memfd()
Date: Wed, 3 Jan 2024 09:43:43 -0800 [thread overview]
Message-ID: <20240103174343.3016720-1-seanjc@google.com> (raw)
Recording and slides of the post-copy for guest_memfd discussion:
https://drive.google.com/corp/drive/folders/1_3bLYrR7oYZ06XvOPY_xZGUApGhq-j3W?resourcekey=0-0C1BYqhodcNvHFIqVwKMTg
Key takeaways:
- There is no known use case for tying "data invalid" to the guest_memfd
inode, i.e. letting each "view" (struct file / struct kvm / VM) control its
own behavior is acceptable, and arguably desirable as it provides userspace
more flexibility.
- If the "data invalid" attribute is tied to a given view, then routing the
ioctl() through KVM provides a superset of functionality compared to making
a guest_memfd specific ioctl(), e.g. KVM can apply the attribute to any gfn
regardless of backing store.
- Pursuing a fully generic file-based solution is undesirable as there are a
large number of questions that need answers, and there is no known use case
beyond KVM to drive those discussions.
Feel free to chime in with anything important that I missed.
reply other threads:[~2024-01-03 17:43 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=20240103174343.3016720-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=aaronlewis@google.com \
--cc=axelrasmussen@google.com \
--cc=dmatlack@google.com \
--cc=isaku.yamahata@linux.intel.com \
--cc=jthoughton@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=yan.y.zhao@intel.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
all inboxes | Powered by JetHome®