From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by mx.groups.io with SMTP id smtpd.web08.5837.1634276767712985158 for ; Thu, 14 Oct 2021 22:46:08 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=RVuX/7XS; spf=pass (domain: redhat.com, ip: 216.205.24.124, mailfrom: kraxel@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1634276766; 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: in-reply-to:in-reply-to:references:references; bh=J/vXUnwJVh2s7g8Xj+Q2EBGx9p2zG08Fgtk/ShZ4/jk=; b=RVuX/7XSW7rXKjOWhzO8mf12fy0X5T0+h6I5YyvShsuB64zZ1ISYcjYt4woDA7PusSavSp ZJ+r5bieIs6O/KRw1JSTD3dSIfgSb3TftQkJWM9GnXRVEQsBzNHAUqBLUB1+2JtAKULuBG JT92hhZ4K9dS+LTvXQWVdg8+XYRlr24= 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-477-KFCROVOyNayFAx_5hu7IKA-1; Fri, 15 Oct 2021 01:46:01 -0400 X-MC-Unique: KFCROVOyNayFAx_5hu7IKA-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id A74A21006AAC; Fri, 15 Oct 2021 05:45:59 +0000 (UTC) Received: from sirius.home.kraxel.org (unknown [10.39.192.23]) by smtp.corp.redhat.com (Postfix) with ESMTPS id E7A7A10013D7; Fri, 15 Oct 2021 05:45:58 +0000 (UTC) Received: by sirius.home.kraxel.org (Postfix, from userid 1000) id 3F0301800393; Fri, 15 Oct 2021 07:45:57 +0200 (CEST) Date: Fri, 15 Oct 2021 07:45:57 +0200 From: "Gerd Hoffmann" To: "Yao, Jiewen" Cc: "devel@edk2.groups.io" , "Xu, Min M" , Ard Biesheuvel , "Justen, Jordan L" , Brijesh Singh , Erdem Aktas , James Bottomley , Tom Lendacky Subject: Re: [edk2-devel] [PATCH V2 21/28] OvmfPkg: Update PlatformPei to support TDX Message-ID: <20211015054557.qwh6qalq5uql4smq@sirius.home.kraxel.org> References: <7a6c9317555de257ad0fd1d76c59c841fa601086.1633401643.git.min.m.xu@intel.com> <20211013044925.edspdvhh5t5baxez@sirius.home.kraxel.org> MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=kraxel@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, > The original mailbox location is in low memory. If we do not relocate > to high memory, then the OS will see a hole in low memory. Well, both low and high memory to be exact. qemu maps the whole firmware image below 4G, and mirrors the topmost 128k (including memfd + reset vector) below 1M. Given that TDX starts the processor in 32bit mode, so it doesn't need the 16bit entry @ f000:fff0, I assumed TDX completely ignores the low memory mapping and uses only the high memory mapping. So you are telling me this is not the case? take care, Gerd