From: "Jörg Rödel" <joro@8bytes.org>
To: linux-coco@lists.linux.dev, svsm-devel@coconut-svsm.dev,
kvm@vger.kernel.org, linux-sgx@vger.kernel.org,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Cc: Dhaval Giani <dhaval.giani@gmail.com>
Subject: [CfP] Confidential Computing Microconference @ LPC 2024
Date: Tue, 4 Jun 2024 16:50:04 +0200 [thread overview]
Message-ID: <Zl8pnPS8EVgFgxSR@8bytes.org> (raw)
Hi,
We are pleased to announce the call for presentations for the
Confidential Computing microconference at the Linux Plumbers Conference,
happening in Vienna from September 18th to 20th.
In this microconference we want to discuss ongoing developments around Linux
support for memory encryption and confidential computing in general.
Topics of interest include:
* Support TEE privilege separation extensions (TDX partitioning and AMD
SEV-SNP VM Privilege Levels) both on the guest and host side.
* Secure IRQ delivery
* Secure VM Service Module (SVSM) support for multiple TEE architectures
* Trusted I/O software architecture
* Live migration of confidential virtual machines
* Remote attestation architectures
* Deployment of Confidential VMs
* Linux as a CVM operating system across hypervisors
* Unification of various confidential computing API
Please use the LPC CfP process to submit your proposals. Submissions can
be made via
https://lpc.events/event/18/abstracts/
Make sure to select "Confidential Computing MC" as the track and submit
your session proposal by July 15th. Submissions made after that date
can not be included into the microconference.
Looking forward to seeing all of you in Vienna in September!
Thanks,
Dhaval and Joerg
reply other threads:[~2024-06-04 14:50 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=Zl8pnPS8EVgFgxSR@8bytes.org \
--to=joro@8bytes.org \
--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=svsm-devel@coconut-svsm.dev \
--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;
as well as URLs for NNTP newsgroup(s).