Linux-Sgx Archive mirror
 help / color / mirror / Atom feed

From: "Jörg Rödel" <joro@8bytes.org>
To: linux-kernel@vger.kernel.org, linux-coco@lists.linux.dev,
	kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
	linux-sgx@vger.kernel.org
Cc: Andi Kleen <ak@linux.intel.com>,
	Andy Lutomirski <luto@kernel.org>, Borislav Petkov <bp@alien8.de>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	David Hildenbrand <david@redhat.com>,
	David Kaplan <David.Kaplan@amd.com>,
	David Rientjes <rientjes@google.com>,
	Joerg Roedel <jroedel@suse.de>,
	Jun Nakajima <jun.nakajima@intel.com>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Marc Orr <marcorr@google.com>, Mike Rapoport <rppt@kernel.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Peter Gonda <pgonda@google.com>,
	Sathya Kuppuswamy <sathyanarayanan.kuppuswamy@intel.com>,
	Sean Christopherson <seanjc@google.com>,
	Tom Lendacky <thomas.lendacky@amd.com>
Subject: [CFP LPC 2022] Confidential Computing Microconference
Date: Fri, 20 May 2022 17:48:17 +0200	[thread overview]
Message-ID: <Yoe4QZr8dqy1hrU1@8bytes.org> (raw)

Hi,

as already announced by the planning committee, there will be another

	Confidential Computing Microconference

at this years Linux Plumbers Conference (LPC) happening from 12th to
14th of September in Dublin, Ireland.

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

Suggested topics are:

	* Design and implementation of Intel TDX and AMD SEV-SNP host
	  support

	* Linux kernel memory management changes for secure execution
	  environments

	* Support of upcoming secure execution hardware extensions
	  from ARM and RISC-V

	* Pre-launch and runtime attestation workflows

	* Interrupt security for AMD SEV-SNP

	* Debuggability and live migration of encrypted virtual machines

	* Proper testing of confidential computing support code

	* Support for Confidential Containers

	* Or anything else related to Confidential Computing in Linux

Please submit your proposals on the LPC website at:

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

Make sure to select "Confidential Computing MC" in the Track pulldown
menu.

Looking forwart to seeing you all there, either in Dublin or virtual :)

Thanks,

	Joerg

next             reply	other threads:[~2022-05-20 15:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20 15:48 Jörg Rödel [this message]
2022-07-25  9:55 ` [CLOSED] Re: [CFP LPC 2022] Confidential Computing Microconference 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=Yoe4QZr8dqy1hrU1@8bytes.org \
    --to=joro@8bytes.org \
    --cc=David.Kaplan@amd.com \
    --cc=ak@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=david@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=jroedel@suse.de \
    --cc=jun.nakajima@intel.com \
    --cc=kirill.shutemov@linux.intel.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=luto@kernel.org \
    --cc=marcorr@google.com \
    --cc=pbonzini@redhat.com \
    --cc=pgonda@google.com \
    --cc=rientjes@google.com \
    --cc=rppt@kernel.org \
    --cc=sathyanarayanan.kuppuswamy@intel.com \
    --cc=seanjc@google.com \
    --cc=thomas.lendacky@amd.com \
    --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).