From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=134.134.136.65; helo=mga03.intel.com; envelope-from=sai.praneeth.prakhya@intel.com; receiver=edk2-devel@lists.01.org Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) (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 B9E8E203B992D for ; Mon, 14 May 2018 16:30:51 -0700 (PDT) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 May 2018 16:30:51 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,402,1520924400"; d="scan'208,217";a="54325309" Received: from orsmsx105.amr.corp.intel.com ([10.22.225.132]) by fmsmga004.fm.intel.com with ESMTP; 14 May 2018 16:30:50 -0700 Received: from orsmsx160.amr.corp.intel.com (10.22.226.43) by ORSMSX105.amr.corp.intel.com (10.22.225.132) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 14 May 2018 16:30:50 -0700 Received: from orsmsx114.amr.corp.intel.com ([169.254.8.24]) by ORSMSX160.amr.corp.intel.com ([169.254.13.99]) with mapi id 14.03.0319.002; Mon, 14 May 2018 16:30:49 -0700 From: "Prakhya, Sai Praneeth" To: "edk2-devel@lists.01.org" CC: "Neri, Ricardo" Thread-Topic: Query regarding hole in EFI Memory Map Thread-Index: AdPr2REpOMPrnedhTWCTzmfX7Cr+ZQ== Date: Mon, 14 May 2018 23:30:49 +0000 Message-ID: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZGRjODg1NTItMmJjZC00NjViLWIzMDMtMGJlYTE2NGU4OTkxIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjIuNS4xOCIsIlRydXN0ZWRMYWJlbEhhc2giOiI3VHNONk96SjFWcHhGTndpaldFUEdGa3hCQ1ZFaFhnSkhjdncyUjQwNWNLT09qd05LZkoyaHpaNTEwc3FoVDJSIn0= x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.200.100 dlp-reaction: no-action x-originating-ip: [10.22.254.140] MIME-Version: 1.0 X-Content-Filtered-By: Mailman/MimeDel 2.1.26 Subject: Query regarding hole in EFI Memory Map X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 May 2018 23:30:51 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi All, Recently, I have observed that there was a hole in EFI Memory Map passed by= firmware to Linux kernel. So, wanted to check with you if this is expected= or not. My Test setup: I usually boot qemu with OVMF and Linux kernel. I use below command to boot= kernel. "qemu-system-x86_64 -cpu host -hda -serial stdio -bios -m 2G -enable-kvm -smp 2" I have noticed that the EFI Memory Map (printed by kernel) is almost contig= uous but with only one hole ranging from 0xA0000 to 0x100000. As far as I k= now, kernel hasn't modified this EFI Memory Map, so I am assuming that firm= ware has passed memory map with a hole. I have looked at UEFI spec "GetMemo= ryMap()" definition, and it says "The map describes all of memory, no matte= r how it is being used". So, I am thinking that EFI Memory Map shouldn't ha= ve any holes, am I correct? If not, could someone please explain me the rea= son for this hole in EFI Memory Map. Please let me know if you want me to post the EFI Memory Map or E820 map th= at I am looking at. Note: I have also observed the same hole in E820 map. Regards, Sai