From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124]) by mx.groups.io with SMTP id smtpd.web12.13290.1604677539604145479 for ; Fri, 06 Nov 2020 07:45:40 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Xj4hQkS4; spf=pass (domain: redhat.com, ip: 63.128.21.124, mailfrom: lersek@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1604677538; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=tUtDFm7k0MC2+ReKauBXLDcLseUx/kpujBk4Z8s4r4k=; b=Xj4hQkS4IQhiUYAKuVTpVSK2ls8i8ycLMYuNAlYOA6+cyEmYQW2Uzu+ogz3HyGld1eFfno QuR1sbQjKup8BdPegwlV5opuk6TneCnxR103tPllJkeKgThaZPfByCDFVkN7dX4SMDrFNQ FBopR6vpM2gYuTgNqXka0NHPx0l088E= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-184-OXSSntVyOt2-KJDaTvmEMA-1; Fri, 06 Nov 2020 10:45:36 -0500 X-MC-Unique: OXSSntVyOt2-KJDaTvmEMA-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 03A621009E2D; Fri, 6 Nov 2020 15:45:35 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-115-95.ams2.redhat.com [10.36.115.95]) by smtp.corp.redhat.com (Postfix) with ESMTP id 2C15126185; Fri, 6 Nov 2020 15:45:31 +0000 (UTC) Subject: Re: [edk2-devel] RFC: Fast Migration for SEV and SEV-ES - blueprint and proof of concept To: Tobin Feldman-Fitzthum Cc: devel@edk2.groups.io, dovmurik@linux.vnet.ibm.com, Dov.Murik1@il.ibm.com, ashish.kalra@amd.com, brijesh.singh@amd.com, tobin@ibm.com, david.kaplan@amd.com, jon.grimm@amd.com, thomas.lendacky@amd.com, jejb@linux.ibm.com, frankeh@us.ibm.com, "Dr. David Alan Gilbert" References: <933a5d2b-a495-37b9-fe8b-243f9bae24d5@redhat.com> <61acbc7b318b2c099a106151116f25ea@linux.vnet.ibm.com> From: "Laszlo Ersek" Message-ID: <25377952-d8cf-3a64-d147-4e99379fa7b8@redhat.com> Date: Fri, 6 Nov 2020 16:45:31 +0100 MIME-Version: 1.0 In-Reply-To: <61acbc7b318b2c099a106151116f25ea@linux.vnet.ibm.com> X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=lersek@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit On 11/04/20 19:27, Tobin Feldman-Fitzthum wrote: > In the meantime, perhaps there is something we can do to help > make our current work more clear. We could potentially explain > things on a call or create some additional documentation. While > our goal is not to shove this version of the trampoline upstream, > it is significant to our plan as a whole and we want to help > people understand it. >>From my personal (selfish) perspective, a call would be counter-productive. Regarding documentation, I do have one thought that might help, with the (very tricky) page table manipulations / phases: diagrams (ascii or svg, perhaps). I don't know if that will help me look at this in detail earlier, but *when* I will look at it, it will definitely help me. (If there are diagrams already, then I apologize for not noticing them.) Thanks! Laszlo