Re: [edk2-devel] [PATCH v1 0/1] Introduce DxeMmUnblockMemoryLib Interface

2021-02-08 Thread Kun Qin
Hi Hao, These 2 modules seems to be the only ones need to be updated when we scrubbed and validated our code base. I will prepare for the tcg2 and variable module patches. Thanks, Kun -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online

Re: [edk2-devel] [PATCH v1 0/1] Introduce DxeMmUnblockMemoryLib Interface

2021-02-06 Thread Wu, Hao A
all the potential modules affected? Best Regards, Hao Wu From: devel@edk2.groups.io On Behalf Of Kun Qin Sent: Saturday, February 6, 2021 10:48 AM To: Wu; Wu, Hao A ; devel@edk2.groups.io Subject: Re: [edk2-devel] [PATCH v1 0/1] Introduce DxeMmUnblockMemoryLib Interface Hi Hao, My plan

Re: [edk2-devel] [PATCH v1 0/1] Introduce DxeMmUnblockMemoryLib Interface

2021-02-05 Thread Kun Qin
Hi Hao, My plan was to follow up with the driver changes regarding Tcg2Smm and VariableSmmRuntimeDxe once this interface is officially checked in. But if it is preferred to submit the patch for Tcg2Smm and VariableSmmRuntimeDxe to make better sense on how this interface will be consumed, I can

Re: [edk2-devel] [PATCH v1 0/1] Introduce DxeMmUnblockMemoryLib Interface

2021-02-04 Thread Wu, Hao A
] [PATCH v1 0/1] Introduce DxeMmUnblockMemoryLib Interface Hi Hao, As mentioned in the cover letter and in BZ-3168, VariableStandaloneMm and Tcg2Smm would need this capability to unblock certain regions in order to access either variable runtime cache or NVS region patched into ACPI table, if non

Re: [edk2-devel] [PATCH v1 0/1] Introduce DxeMmUnblockMemoryLib Interface

2021-02-04 Thread Kun Qin
Hi Hao, As mentioned in the cover letter and in BZ-3168, VariableStandaloneMm and Tcg2Smm would need this capability to unblock certain regions in order to access either variable runtime cache or NVS region patched into ACPI table, if non-MMRAM region is blocked for access. Just as a preview

Re: [edk2-devel] [PATCH v1 0/1] Introduce DxeMmUnblockMemoryLib Interface

2021-02-04 Thread Wu, Hao A
> -Original Message- > From: devel@edk2.groups.io On Behalf Of Sean > Sent: Friday, February 5, 2021 10:37 AM > To: devel@edk2.groups.io; Wu, Hao A ; > ku...@outlook.com; Yao, Jiewen > Cc: Wang, Jian J ; Dong, Eric ; > Ni, Ray > Subject: Re: [edk2-devel]

Re: [edk2-devel] [PATCH v1 0/1] Introduce DxeMmUnblockMemoryLib Interface

2021-02-04 Thread Sean
Hao wu, I agree that for reviewing this change that would provide more confidence. The real issue is that there is no x64 mm standalone solution that blocks memory access in edk2 today. So implementing this interface in edk2 doesn't make sense. It would just rot with no users, validation, or

Re: [edk2-devel] [PATCH v1 0/1] Introduce DxeMmUnblockMemoryLib Interface

2021-02-04 Thread Wu, Hao A
> -Original Message- > From: devel@edk2.groups.io On Behalf Of Kun Qin > Sent: Wednesday, February 3, 2021 6:16 AM > To: devel@edk2.groups.io > Cc: Wang, Jian J ; Wu, Hao A ; > Dong, Eric ; Ni, Ray ; Yao, Jiewen > > Subject: [edk2-devel] [PATCH v1 0/1] Introduce DxeMmUnblockMemoryLib >