From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from muon.cran.org.uk (muon.bluestop.org [74.50.51.35]) (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 5BE78208F7AD4 for ; Wed, 9 Aug 2017 13:44:58 -0700 (PDT) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id 264AE98D01; Wed, 9 Aug 2017 20:47:16 +0000 (UTC) Received: from muon.cran.org.uk ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id GqDEbjcMmXdS; Wed, 9 Aug 2017 20:47:15 +0000 (UTC) Received: from [192.168.1.67] (c-73-131-237-119.hsd1.ut.comcast.net [73.131.237.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA; Wed, 9 Aug 2017 20:47:15 +0000 (UTC) To: edk2-devel@lists.01.org Cc: lersek@redhat.com From: Rebecca Cran Message-ID: <34458438-9913-6bab-0ddb-e2908ddd006a@bluestop.org> Date: Wed, 9 Aug 2017 14:47:14 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 Subject: OvmfPkg (PlatformPei?): supporting Qemu's nvdimm device 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: Wed, 09 Aug 2017 20:44:58 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US I've been investigating adding support for Qemu's nvdimm devices to OVMF. I was thinking such support would go into PlatformPei, but it looks like I can only read the ACPI NFIT in the DXE phase. So, should Qemu be changed to add non-volatile memory to the e820 table, or should such memory be added during the DXE phase instead? -- Rebecca