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 7B54E21CF25A3 for ; Fri, 7 Jul 2017 19:10:40 -0700 (PDT) Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 23AD83680C; Sat, 8 Jul 2017 02:12:22 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 23AD83680C Authentication-Results: ext-mx06.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx06.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=lersek@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 23AD83680C Received: from lacos-laptop-7.usersys.redhat.com (ovpn-116-228.phx2.redhat.com [10.3.116.228]) by smtp.corp.redhat.com (Postfix) with ESMTP id 2D4FA78389; Sat, 8 Jul 2017 02:12:18 +0000 (UTC) To: Jiewen Yao From: Laszlo Ersek Cc: edk2-devel-01 Message-ID: Date: Sat, 8 Jul 2017 04:12:17 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Sat, 08 Jul 2017 02:12:22 +0000 (UTC) X-Content-Filtered-By: Mailman/MimeDel 2.1.22 Subject: memory protection crash in PiSmmCpuDxeSmm, Ia32 build with RAM above 4GB 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: Sat, 08 Jul 2017 02:10:40 -0000 Content-Language: en-US Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi Jiewen, I just noticed that building OvmfIa32.dsc with -D SMM_REQUIRE, and then running the 32-bit guest with 4G RAM (of which 2GB are placed in 64-bit address pace), the guest crashes when PiSmmCpuDxeSmm tries to protect the memory range at 4GB. Please find the log attached (it ends with the crash). Is this expected to work? Thanks Laszlo