From: Sean Christopherson <seanjc@google.com>
To: kvm@vger.kernel.org
Cc: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Sagi Shahar <sagis@google.com>,
Erdem Aktas <erdemaktas@google.com>,
Anish Ghulati <aghulati@google.com>,
Oliver Upton <oliver.upton@linux.dev>,
James Houghton <jthoughton@google.com>,
Anish Moorthy <amoorthy@google.com>,
Ben Gardon <bgardon@google.com>,
David Matlack <dmatlack@google.com>,
Ricardo Koller <ricarkol@google.com>,
Axel Rasmussen <axelrasmussen@google.com>,
Aaron Lewis <aaronlewis@google.com>,
Ashish Kalra <ashish.kalra@amd.com>,
Babu Moger <babu.moger@amd.com>, Chao Gao <chao.gao@intel.com>,
Chao Peng <chao.p.peng@linux.intel.com>,
Chenyi Qiang <chenyi.qiang@intel.com>,
David Woodhouse <dwmw@amazon.co.uk>,
Emanuele Giuseppe Esposito <eesposit@redhat.com>,
Gavin Shan <gshan@redhat.com>, Guang Zeng <guang.zeng@intel.com>,
Hou Wenlong <houwenlong.hwl@antgroup.com>,
Jiaxi Chen <jiaxi.chen@linux.intel.com>,
Jim Mattson <jmattson@google.com>, Jing Liu <jing2.liu@intel.com>,
Junaid Shahid <junaids@google.com>,
Kai Huang <kai.huang@intel.com>,
Leonardo Bras <leobras@redhat.com>,
Like Xu <like.xu.linux@gmail.com>,
Li RongQing <lirongqing@baidu.com>,
"Maciej S . Szmigiero" <maciej.szmigiero@oracle.com>,
Maxim Levitsky <mlevitsk@redhat.com>,
Michael Roth <michael.roth@amd.com>, Michal Luczaj <mhal@rbox.co>,
Mingwei Zhang <mizhang@google.com>,
Nikunj A Dadhania <nikunj@amd.com>,
Paul Durrant <pdurrant@amazon.com>,
Peng Hao <flyingpenghao@gmail.com>,
Peter Gonda <pgonda@google.com>, Peter Xu <peterx@redhat.com>,
Robert Hoo <robert.hu@linux.intel.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Vipin Sharma <vipinsh@google.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Wei Wang <wei.w.wang@intel.com>,
Xiaoyao Li <xiaoyao.li@intel.com>,
Yu Zhang <yu.c.zhang@linux.intel.com>,
Will Deacon <will@kernel.org>, Marc Zyngier <maz@kernel.org>,
David Hildenbrand <david@redhat.com>,
Fuad Tabba <tabba@google.com>,
Isaku Yamahata <isaku.yamahata@gmail.com>,
Qinglan Xiang <qinglan.xiang@intel.com>,
Kai Svahn <kai.svahn@intel.com>,
Margarita Maroto <margarita.maroto@intel.com>,
Anil Keshavamurthy <anil.s.keshavamurthy@intel.com>,
Nagareddy Reddy <nspreddy@google.com>,
linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] PUCK Agenda - 2023.05.31 - guest_memfd()
Date: Thu, 25 May 2023 16:47:35 -0700 [thread overview]
Message-ID: <20230525234735.2585977-1-seanjc@google.com> (raw)
Topic: guest_memfd(), a.k.a. restrictedmem, a.k.a. UPM
Objective: Reach consensus on design for backing guest private memory
Background: https://lore.kernel.org/all/ZEM5Zq8oo+xnApW9@google.com
Date: 2023.05.31 (May 31st)
Time: 6am PDT
Video: https://meet.google.com/vdb-aeqo-knk
Phone: https://tel.meet/vdb-aeqo-knk?pin=3003112178656
Future Schedule:
June 7th - pKVM on x86 (Google + Intel)
June 14th - Available!
June 21st - No Meeting (Sean OOO)
June 28th - Available!
July 5th - No Meeting (Sean OOO)
I've created a shared calendar (comically long link at the bottom) that people
can subscribe to in order to get reminders, notifications, etc. At least, that's
the theory. Holler if it's not working as intended and/or if it's insufficient.
Contact me (off-list or on-list, your choice) if you have a topic you'd like to
discuss (see above for available dates). I can't promise that I'll accept all
proposed topics, but at this point the future schedule is quite open :-) When
proposing a topic, please provide background info/links and a clear statement on
exactly what you hope to achieve, e.g. if the goal is to get help solving a
technical problem, get feedback on a direction, reach consensus on something, etc.
My goal is to make PUCK as interactive and informal as possible. To that end,
formal presentations are discouraged, but not outright banned. Though if you
show up with a big slide deck, I may kick you out of the meeting on principal :-).
Time slots are very flexible (within the 1 hour hard limit), but please try to
make a semi-accurate estimate of how much time a topic will need. If there is
unclaimed/unused time (or even no topic) for a given instance, my plan is to use
the time for "office hours", e.g. to answer general upstreaming questions, etc.
At this point, I'm not planning on canceling instances if there's no topic, i.e.
will still hold office hours, though that may change if the office hours idea
isn't useful.
People on the Cc list: for my own sanity, future announcements will be sent only
to kvm@ and LKML. Please either subscribe to the KVM mailing list or the shared
calendar below (or bribe someone to forward you announcements) if you want notificatons.
https://calendar.google.com/calendar/u/0?cid=Y182MWE1YjFmNjQ0NzM5YmY1YmVkN2U1ZWE1ZmMzNjY5Y2UzMmEyNTQ0YzVkYjFjN2M4OTE3MDJjYTUwOTBjN2Q1QGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20
reply other threads:[~2023-05-25 23: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=20230525234735.2585977-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=aaronlewis@google.com \
--cc=aghulati@google.com \
--cc=amoorthy@google.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=ashish.kalra@amd.com \
--cc=axelrasmussen@google.com \
--cc=babu.moger@amd.com \
--cc=bgardon@google.com \
--cc=chao.gao@intel.com \
--cc=chao.p.peng@linux.intel.com \
--cc=chenyi.qiang@intel.com \
--cc=david@redhat.com \
--cc=dmatlack@google.com \
--cc=dwmw@amazon.co.uk \
--cc=eesposit@redhat.com \
--cc=erdemaktas@google.com \
--cc=flyingpenghao@gmail.com \
--cc=gshan@redhat.com \
--cc=guang.zeng@intel.com \
--cc=houwenlong.hwl@antgroup.com \
--cc=isaku.yamahata@gmail.com \
--cc=jiaxi.chen@linux.intel.com \
--cc=jing2.liu@intel.com \
--cc=jmattson@google.com \
--cc=jthoughton@google.com \
--cc=junaids@google.com \
--cc=kai.huang@intel.com \
--cc=kai.svahn@intel.com \
--cc=kvm@vger.kernel.org \
--cc=leobras@redhat.com \
--cc=like.xu.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=maciej.szmigiero@oracle.com \
--cc=margarita.maroto@intel.com \
--cc=maz@kernel.org \
--cc=mhal@rbox.co \
--cc=michael.roth@amd.com \
--cc=mizhang@google.com \
--cc=mlevitsk@redhat.com \
--cc=nikunj@amd.com \
--cc=nspreddy@google.com \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=pdurrant@amazon.com \
--cc=peterx@redhat.com \
--cc=pgonda@google.com \
--cc=qinglan.xiang@intel.com \
--cc=ricarkol@google.com \
--cc=robert.hu@linux.intel.com \
--cc=sagis@google.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=tabba@google.com \
--cc=thomas.lendacky@amd.com \
--cc=vipinsh@google.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=wei.w.wang@intel.com \
--cc=will@kernel.org \
--cc=xiaoyao.li@intel.com \
--cc=yu.c.zhang@linux.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®