Hi Jiewen - I think you meant QueryVariableInfo. I was confused by the language in the notes because I took garbage collection to refer the active process that occurs during this function. There is no active garbage collection in the EDK2 implementation of this function. There is record keeping related to dealing with the deleted copies of old variables.
I think I understand now. Thanks, Tim From: Yao, Jiewen <[email protected]> Sent: Wednesday, July 29, 2026 6:35 PM To: Tim Lewis <[email protected]>; [email protected] Subject: Re: [edk2-devel] EDK2 PQC meeting minutes - July 29, 2026 You don't often get email from [email protected]<mailto:[email protected]>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Hi Tim Please allow me to clarify: GetVariableInfo() is already in UEFI specification today. What we have discussed is: if we need update the GetVariableInfo() in UEFI specification to mention the garbage collection behavior. Now, we think the answer is NO, because garbage collection is EDK2 implementation. We should not update the spec for an implementation. The future plan is to update EDK2 implementation if there is any need. There is no need to change UEFI specification language in this particular case. Please feel free to propose if you have any idea how to improve the API later. Thank you Yao, Jiewen ________________________________ From: Tim Lewis <[email protected]<mailto:[email protected]>> Sent: Thursday, July 30, 2026 2:21 AM To: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>; Yao, Jiewen <[email protected]<mailto:[email protected]>> Subject: RE: [edk2-devel] EDK2 PQC meeting minutes - July 29, 2026 Since we are asking 3rd parties to use this function at runtime (i.e. the OS or even 3rd party utilities), how can it be outside the UEFI specification? It seems like an inter-op question. The normal opinion before was: if non-system-BIOS is going to call an API, it must be documented in the UEFI specification. Thanks, Tim From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> On Behalf Of Yao, Jiewen via groups.io Sent: Wednesday, July 29, 2026 9:18 AM To: [email protected]<mailto:[email protected]> Subject: [edk2-devel] EDK2 PQC meeting minutes - July 29, 2026 0）Open GetVariableInfo() proposal Current thought is to do it via EDK2, not UEFI spec. The goal is to tell how much space about garbage collection (about DBX), because we have single variable write. But the garbage collection is EDK2 implementation, not mentioned in UEFI spec. The expectation is that GetVariableInfo() will trigger garbage collection. If a platform does not trigger garbage collection timely, then we just get smaller NV space at runtime. NOTE: We cannot always trigger garbage collection at boot, because we will have performance issue, or flash wear-out concern. 1) Backlog review https://github.com/orgs/tianocore/projects/10/views/1 Image Validation Result Table - https://github.com/tianocore/edk2/issues/12916 See review comment and discussion at https://github.com/tianocore/edk2/issues/12916#issuecomment-5120451634 Overall the design is good. AR: Joey to prepare PR for review next week. 2) Old issue refresh IEIT removal - https://github.com/tianocore/edk2/issues/12688 No time to review. Defer to the next week. multiple signature format - https://github.com/jyao1/UEFI-Specification-Release/pull/1 No time to review. Defer to the next week. 3) Some idea for image verification https://github.com/microsoft/mu_basecore/pull/1809 https://github.com/Javagedes/mu_basecore/tree/personal/joeyvagedes/securitypkg-image-validation/SecurityPkg/Test/ShellTest/ImageValidationTestApp#all-tests No time to review. Defer to the next week. Thank you Yao, Jiewen -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#122052): https://edk2.groups.io/g/devel/message/122052 Mute This Topic: https://groups.io/mt/120505396/21656 Group Owner: [email protected] Unsubscribe: https://edk2.groups.io/g/devel/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
