From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mx.groups.io with SMTP id smtpd.web09.59003.1638179425146039289 for ; Mon, 29 Nov 2021 01:50:25 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=IqY7e5sA; spf=pass (domain: redhat.com, ip: 170.10.133.124, mailfrom: kraxel@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1638179423; 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=HjM6JuyxaAkcnt/bl+gfhahXrTbL2aqwpnWRY3HWOQ8=; b=IqY7e5sACsPhWEBwhY3Y5noXFmCufVEGf7WngaoHvJq5XB8E1fXtCJnH+Dl0H57ci/SnH5 UxWDKef/9caDAf2XtHA/EOSx8NhEytoLYQXz9UtDoOGWqveT8TgI8F1ZQHdFe3s2qk8uJM Ju5gVfHZyacwJ13lJ18h9nBxT746EV4= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-150-wwSqD3VCNaa9gEfjTN0y3g-1; Mon, 29 Nov 2021 04:50:21 -0500 X-MC-Unique: wwSqD3VCNaa9gEfjTN0y3g-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 9B5BA1006AA0; Mon, 29 Nov 2021 09:50:20 +0000 (UTC) Received: from sirius.home.kraxel.org (unknown [10.39.192.79]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 139C3171FF; Mon, 29 Nov 2021 09:50:20 +0000 (UTC) Received: by sirius.home.kraxel.org (Postfix, from userid 1000) id 63307180079D; Mon, 29 Nov 2021 10:50:18 +0100 (CET) Date: Mon, 29 Nov 2021 10:50:18 +0100 From: "Gerd Hoffmann" To: Andrew Fish Cc: edk2-devel-groups-io , maobibo@loongson.cn Subject: Re: [edk2-devel] one possible issue with ovmf fvb Message-ID: <20211129095018.o2nmxvzmxegqlfbh@sirius.home.kraxel.org> References: <444f3f42-cc2c-f255-389e-504b31789fcd@loongson.cn> <013FF567-925B-457E-88EA-0D623F8D43A0@apple.com> MIME-Version: 1.0 In-Reply-To: <013FF567-925B-457E-88EA-0D623F8D43A0@apple.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 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=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit Hi, > On real X64 hardware you can’t be in 64-bit mode without pageables, > and you can’t put pageables in the ROM. Thus PEI ends up being IA32 > (i386) and this usually means the DXE Core gets loaded < 4 GiB, and > the initial memory map for DXE is memory < 4 GiB. Well, to exact there are two variants, one with PEI being IA32 (OvmfPkgIa32X64.dsc) and the other with PEI being X64 (OvmfPkgX64.dsc). The latter does page table setup and switch to long mode in ResetVector code. But, yes, on both cases the firmware volume with PEI+DXE ends up being loaded below 4 GiB. take care, Gerd