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>,
Michael Roth <michael.roth@amd.com>,
Jason Gunthorpe <jgg@nvidia.com>
Subject: [ANNOUNCE] PUCK Agenda - 2024.01.03 - Post-copy for guest_memfd()
Date: Tue, 2 Jan 2024 09:47:22 -0800 [thread overview]
Message-ID: <20240102174722.2855087-1-seanjc@google.com> (raw)
Tomorrow's PUCK topic is post-copy demand paging for guest_memfd(), courtesty of
David M:
https://lore.kernel.org/all/CALzav=d23P5uE=oYqMpjFohvn0CASMJxXB_XEOEi-jtqWcFTDA@mail.gmail.com
Folks on the Cc, please peek at the future schedule and holler if you have a
conflict for a topic that requires your attendance.
P.S. Someone please remind me to record tomorrow's discussion, I give myself
50:50 odds of remembering to hit record.
Time: 6am PDT
Video: https://meet.google.com/vdb-aeqo-knk
Phone: https://tel.meet/vdb-aeqo-knk?pin=3003112178656
Calendar: https://calendar.google.com/calendar/u/0?cid=Y182MWE1YjFmNjQ0NzM5YmY1YmVkN2U1ZWE1ZmMzNjY5Y2UzMmEyNTQ0YzVkYjFjN2M4OTE3MDJjYTUwOTBjN2Q1QGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20
Drive: https://drive.google.com/drive/folders/1aTqCrvTsQI9T4qLhhLs_l986SngGlhPH?resourcekey=0-FDy0ykM3RerZedI8R-zj4A&usp=drive_link
Future Schedule:
January 10th - Unified uAPI for protected VMs
January 17th - TDP MMU for IOMMU
January 24th - Memtypes for non-coherent DMA
January 31st - Available!
reply other threads:[~2024-01-02 17:47 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=20240102174722.2855087-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=jgg@nvidia.com \
--cc=jthoughton@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=michael.roth@amd.com \
--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®