From: "Jörg Rödel" <joro@8bytes.org>
To: linux-coco@lists.linux.dev, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
coconut-svsm@lists.linux.dev, linux-sgx@vger.kernel.org
Cc: Dhaval Giani <dhaval.giani@gmail.com>
Subject: [CfP] Confidential Computing Microconference (LPC 2026)
Date: Thu, 4 Jun 2026 20:29:46 +0200 [thread overview]
Message-ID: <aiHCZo2BWj0MaJLQ@8bytes.org> (raw)
Hi everyone,
We are pleased to officially open the Call for Presentations for the 2026
Confidential Computing Microconference at LPC this year. LPC will take place
from October 5th to 7th in Prague.
Our goal is to bring open-source developers and industry experts together for
productive discussions that lead to concrete solutions. We are looking for
interactive discussions, ongoing development topics, and problem-solving
sessions rather than static status updates.
We are looking for proposals covering, but not limited to, the following
developments and challenges:
* Enhancements to CVM memory backing via `guest_memfd`
* KVM Support for ARM CCA
* Privilege separation features in KVM
* CVM live migration
* Secure VM Service Module (SVSM) architecture and Linux support
* Trusted I/O software architecture
* Solutions for the full CVM (remote) attestation problem
* Linux as a CVM operating system across hypervisors
* CVM Performance optimization and benchmarking
If you are working on any of these areas or have another critical Confidential
Computing topic that requires community alignment, please submit your proposal!
LPC microconferences are built around discussion and collaboration. Proposals
should focus on open problems, architectural roadblocks, or design choices that
would benefit from in-person feedback from the community.
* Submit here: https://lpc.events/event/20/abstracts/
* Submission Deadline: August 7, 2026
Make sure to select "Confidential Computing MC" as the track! This year the LPC
organization committee will grant pre-registration vouchers to anyone who has
submitted a topic. These are at the usual price ($600) which must be used
before registration opens. If your topic is not accepted you should be eligible
for a refund if your employer doesn’t approve your travel. For more details see
https://lpc.events/blog/current/index.php/2026/04/06/changes-to-registration-availability-for-2026/
Looking forward to seeing you there,
- Dhaval and Joerg
reply other threads:[~2026-06-04 18:29 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=aiHCZo2BWj0MaJLQ@8bytes.org \
--to=joro@8bytes.org \
--cc=coconut-svsm@lists.linux.dev \
--cc=dhaval.giani@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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