Messages in this thread | | | Date | Tue, 3 Dec 2013 12:20:21 +0900 | From | Yasuaki Ishimatsu <> | Subject | Re: [PATCH] x86, efi: add efi_whitelist_table to use all efi variable storage |
| |
(2013/11/23 2:47), Matthew Garrett wrote: > On Fri, 2013-11-22 at 15:29 +0900, Yasuaki Ishimatsu wrote: > >> + DMI_MATCH(DMI_SYS_VENDOR, "FUJITSU"), >> + DMI_MATCH(DMI_PRODUCT_NAME, "PRIMEQUEST"), > > Can we guarantee that no Primequests have this issue? Can we guarantee > that that no prior firmware versions have this issue? Can we guarantee > that no future firmware versions will have this issue? >
Sorry for the late reply. I contacted our firmware team to confirm them. They said that current implementation, thereshold is 5KB, is strange.
Currently many EFI firmwares are based on EFI Development Kit (EDK). Accoding to EDK source, gc on boot time runs when free space of nvram is less than MaximumVariableSize of QueryVariableInfo(). In my system MaximumVariableSize is 1KB. So when free space reaches less than 5KB and I reboot the system, gc does not run on boot time in my system.
Threshold of gc depends on a system. So at least, 5KB threshold must be changed on each system.
Thanks, Yasuaki Ishimatsu
| |