On Thu, 2 Jun 2022 at 19:40, Guilherme G. Piccoli <gpiccoli@xxxxxxxxxx> wrote: > > Hi Ard, apologies for annoying! > No worries, just very busy :-) > Just a friendly ping asking if you have any opinions about these patches. > Honestly, I'm not sure I see the value of this. You want to 'notify the UEFI firmware' but the firmware doesn't really care about these variables, only your bespoke tooling does. EFI pstore captures far more data, so if you just wipe /sys/fs/pstore after each clean boot, you already have all the data you need, no? Also, I'm in the process of removing the public efivar_entry_xxx() API - please look at the efi/next tree for a peek. This is related to your point 3), i.e., the efivar layer is a disaster in terms of consistency between different observers of the EFI variable store. Switching to efivar_set_variable() [the new API] should fix that.
