Linux Confidential Computing Development
 help / color / mirror / Atom feed

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,
	linux-sgx@vger.kernel.org
Cc: Dhaval Giani <dhaval.giani@gmail.com>
Subject: [CfP] Confidential Computing Microconference @ LPC 2023
Date: Thu, 13 Jul 2023 17:50:23 +0200	[thread overview]
Message-ID: <ZLAdPyqn8glGgYjT@8bytes.org> (raw)

Hi,

We are pleased to announce the call for presentations for this years
Confidential Computing MC at the Linux Plumbers Conference.

In this microconference we want to discuss ongoing developments around
Linux support for memory encryption and support for confidential
computing in general.

Topics of interest include:

	* Support for unaccepted memory

	* Attestation workflows

	* Confidential Computing threat model

	* Secure VM Service module (SVSM) and paravisor architecture and implementation

	* Live migration of confidential virtual machines

	* ARM64 Confidential Computing

	* RISC-V CoVE

	* Secure IO and device attestation

	* Intel TDX Connect

	* AMD SEV-TIO

Please use the LPC CfP process to submit your proposals. Submissions can
be made via

	https://lpc.events/event/17/abstracts/

Make sure to select "Confidential Computing MC" as the track and submit
your session proposal by August 25th. Submissions made after that date
can not be included into the microconference.

Looking forward to seeing all of you in Richmond, Virginia in November!

Thanks,

	Joerg

next             reply	other threads:[~2023-07-13 15:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-13 15:50 Jörg Rödel [this message]
2023-08-25 13:16 ` [CfP] Confidential Computing Microconference @ LPC 2023 Jörg Rödel

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=ZLAdPyqn8glGgYjT@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=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

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 read-only IMAP folder(s) and NNTP newsgroup(s).