From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: redhat.com, ip: 209.132.183.28, mailfrom: lersek@redhat.com) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by groups.io with SMTP; Fri, 23 Aug 2019 05:40:28 -0700 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 682E4881345; Fri, 23 Aug 2019 12:40:28 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-117-39.ams2.redhat.com [10.36.117.39]) by smtp.corp.redhat.com (Postfix) with ESMTP id 38ADC5D6D0; Fri, 23 Aug 2019 12:40:26 +0000 (UTC) Subject: Re: [edk2-devel] [Patch] MdeModulePkg DxeCore: Fix for missing MAT update To: "Gao, Liming" Cc: "devel@edk2.groups.io" , "Kinney, Michael D" , Mike Turner , "Wang, Jian J" , "Wu, Hao A" , "Bi, Dandan" , Anthony Perard , "Justen, Jordan L" References: <20190810141022.18228-1-liming.gao@intel.com> <66665886-fff1-248a-77e5-6b8fb6966f86@redhat.com> <96f6e8a3-7049-478a-a8f2-4389c06f0e12@redhat.com> <4A89E2EF3DFEDB4C8BFDE51014F606A14E4D0EE7@SHSMSX104.ccr.corp.intel.com> <28d0e7fa-35c8-ca4b-a476-3afdd5d1c3a2@redhat.com> <4A89E2EF3DFEDB4C8BFDE51014F606A14E4D101F@SHSMSX104.ccr.corp.intel.com> <684cdd50-88d7-500e-ca56-c59f11e0e615@redhat.com> <4A89E2EF3DFEDB4C8BFDE51014F606A14E4D28C7@SHSMSX104.ccr.corp.intel.com> <5e9663fa-7f62-d510-ae4a-389554a578e8@redhat.com> <4A89E2EF3DFEDB4C8BFDE51014F606A14E4D31DA@SHSMSX104.ccr.corp.intel.com> <3ab30114-ec82-aaec-cd8a-016c351012e4@redhat.com> <4A89E2EF3DFEDB4C8BFDE51014F606A14E4D956E@SHSMSX104.ccr.corp.intel.com> <46ef6b76-568e-75e8-fe72-c09dfe584158@redhat.com> <4A89E2EF3DFEDB4C8BFDE51014F606A14E4DAF85@SHSMSX104.ccr.corp.intel.com> From: "Laszlo Ersek" Message-ID: Date: Fri, 23 Aug 2019 14:40:24 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E4DAF85@SHSMSX104.ccr.corp.intel.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (mx1.redhat.com [10.5.110.69]); Fri, 23 Aug 2019 12:40:28 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit On 08/22/19 16:52, Gao, Liming wrote: >> -----Original Message----- >> From: Laszlo Ersek [mailto:lersek@redhat.com] >> Sent: Thursday, August 22, 2019 7:56 PM >> To: Gao, Liming >> Cc: devel@edk2.groups.io; Kinney, Michael D ; Mike Turner ; Wang, Jian J >> ; Wu, Hao A ; Bi, Dandan ; Anthony Perard >> ; Justen, Jordan L >> Subject: Re: [edk2-devel] [Patch] MdeModulePkg DxeCore: Fix for missing MAT update >> This is the current status: >> >> - OvmfXen: >> - runs in Xen HVM guests >> - runs in Xen PVH guests >> >> - traditional OVMF >> - runs in Xen HVM guests >> - runs in QEMU/KVM guests >> >> The desired (and agreed upon) end-status is the following: >> >> - OvmfXen: >> - runs in Xen HVM guests >> - runs in Xen PVH guests >> >> - traditional OVMF >> - runs in QEMU/KVM guests >> >> (This will match the platform separation that we have under ArmVirtPkg too.) >> >> Anthony plans to remove the Xen HVM code from traditional OVMF in a year >> or so, if I understand correctly. That's when "traditional OVMF" will >> become QEMU/KVM-only, completing the separation. And that's when I >> expect we can fix TianoCore#386 for QEMU/KVM *only*, without Jordan >> NACKing the patch set. >> > Ok. Is there BZ for this change? The contributor can propose his work planning. > Then, I will update edk2 feature planning wiki. I've now reported: https://bugzilla.tianocore.org/show_bug.cgi?id=2122 and assigned it to Anthony. (Anthony, I hope that's OK with you.) >> Basically, "PcdMemVarstoreEmuEnable" would be constant TRUE in OvmfXen >> (inherited from the OVMF DEC file), and it would be exposed to the >> platform builder via "-D MEM_VARSTORE_EMU_ENABLE=FALSE" in the "OVMF for >> QEMU/KVM" platform. FaultTolerantWritePei and VariablePei would be >> included in the "OVMF for QEMU/KVM" DSC files only, and so on. >> > I think this design meets with the request BZ386. I've also reopened https://bugzilla.tianocore.org/show_bug.cgi?id=386 now (moving it back to CONFIRMED state, from RESOLVED|WONTFIX), and I've made it dependent on TianoCore#2122. Thanks, Laszlo