From: Alexander Graf <graf@amazon.com>
To: Dan Middleton <dan.middleton@linux.intel.com>,
<linux-coco@lists.linux.dev>,
"Kalra, Ashish" <ashish.kalra@amd.com>
Subject: Re: Confidential Computing call May 10: RTMR ABI & TEE I/O
Date: Fri, 7 Jun 2024 16:24:37 +0200 [thread overview]
Message-ID: <0ebfe6b4-ee5d-4909-8a3b-bbc1bd7623c7@amazon.com> (raw)
In-Reply-To: <61b65115-5945-4e27-89e4-bb6cba657f7f@linux.intel.com>
Hi Dan,
On 03.05.24 21:55, Dan Middleton wrote:
>
> Hi
> Next Friday, May 10th at 9am PDT, we have a Confidential Computing
> devsec / BoF / Discussion Group / SIG call. Everyone is welcome.
>
> Tentative agenda includes RTMR ABI v3 direction and TEE I/O next steps.
I haven't seen an email for today's call, so let me throw my topic
suggestion here:
I would like to talk about "confidential kexec" today: A kexec mechanism
that allows you to destroy the confidential VM you're in and recreate a
new one based on a payload of the old one. With that, we would have a
very easy and clean mechanism to bootstrap a VM into a fully measured
new execution stack.
Thanks,
Alex
Amazon Web Services Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss
Eingetragen am Amtsgericht Charlottenburg unter HRB 257764 B
Sitz: Berlin
Ust-ID: DE 365 538 597
next prev parent reply other threads:[~2024-06-07 14:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 19:55 Confidential Computing call May 10: RTMR ABI & TEE I/O Dan Middleton
2024-05-07 16:17 ` James Bottomley
2024-05-13 5:10 ` Samuel Ortiz
2024-06-07 14:24 ` Alexander Graf [this message]
2024-06-07 14:46 ` Reshetova, Elena
2024-06-07 16:05 ` Alexander Graf
2024-06-08 14:41 ` James Bottomley
2024-06-10 12:09 ` Alexander Graf
2024-06-12 12:48 ` James Bottomley
2024-06-12 11:19 ` Reshetova, Elena
2024-06-12 11:49 ` Alexander Graf
2024-06-12 13:19 ` Reshetova, Elena
2024-06-12 21:18 ` Steve Rutherford
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=0ebfe6b4-ee5d-4909-8a3b-bbc1bd7623c7@amazon.com \
--to=graf@amazon.com \
--cc=ashish.kalra@amd.com \
--cc=dan.middleton@linux.intel.com \
--cc=linux-coco@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.