From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 2E9E221DF807A for ; Mon, 28 Aug 2017 01:40:40 -0700 (PDT) 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 mx1.redhat.com (Postfix) with ESMTPS id EB9F261460; Mon, 28 Aug 2017 08:43:18 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com EB9F261460 Authentication-Results: ext-mx10.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx10.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=lersek@redhat.com Received: from lacos-laptop-7.usersys.redhat.com (ovpn-116-67.phx2.redhat.com [10.3.116.67]) by smtp.corp.redhat.com (Postfix) with ESMTP id F1B3717126; Mon, 28 Aug 2017 08:43:17 +0000 (UTC) To: edk2-devel-01 Cc: Michael Kinney , "Gao, Liming" , Ard Biesheuvel From: Laszlo Ersek Message-ID: <1714bf60-83a1-ce07-1d71-ac729d8e9dc8@redhat.com> Date: Mon, 28 Aug 2017 10:43:16 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.39]); Mon, 28 Aug 2017 08:43:19 +0000 (UTC) Subject: "practical" memory allocation limit? X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Aug 2017 08:40:40 -0000 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Hi, I've been curious about it for a long time, so I guess I might as well ask the question: Even if OVMF's DXE phase is built for X64, and even if I give the VM memory above 4GB -- confirmed by the MEMMAP command in the UEFI shell --, in the OVMF log I see practically all allocations coming from the 32-bit address space. OVMF produces all its memory resource descriptor HOBs in PEI, all "tested". (No memory is added in DXE.) So why aren't DXE allocations served from 64-bit space? Something seems to be artificially limiting run-of-the-mill pool and page allocations in X64 OVMF; what is it? (It doesn't work like this in ArmVirtQemu.) Thanks! Laszlo