Searched hist:"472831 d4c4b2d8eac783b256e5c829487d5310df" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/drivers/firmware/efi/ |
| H A D | vars.c | diff 472831d4c4b2d8eac783b256e5c829487d5310df Mon Jun 20 06:17:20 CDT 2022 Ard Biesheuvel <ardb@kernel.org> efi: vars: Add thin wrapper around EFI get/set variable interface
The current efivars layer is a jumble of list iterators, shadow data
structures and safe variable manipulation helpers that really belong in
the efivarfs pseudo file system once the obsolete sysfs access method to
EFI variables is removed.
So split off a minimal efivar get/set variable API that reuses the
existing efivars_lock semaphore to mediate access to the various runtime
services, primarily to ensure that performing a SetVariable() on one CPU
while another is calling GetNextVariable() in a loop to enumerate the
contents of the EFI variable store does not result in surprises.
Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
|
| /openbmc/linux/include/linux/ |
| H A D | efi.h | diff 472831d4c4b2d8eac783b256e5c829487d5310df Mon Jun 20 06:17:20 CDT 2022 Ard Biesheuvel <ardb@kernel.org> efi: vars: Add thin wrapper around EFI get/set variable interface
The current efivars layer is a jumble of list iterators, shadow data
structures and safe variable manipulation helpers that really belong in
the efivarfs pseudo file system once the obsolete sysfs access method to
EFI variables is removed.
So split off a minimal efivar get/set variable API that reuses the
existing efivars_lock semaphore to mediate access to the various runtime
services, primarily to ensure that performing a SetVariable() on one CPU
while another is calling GetNextVariable() in a loop to enumerate the
contents of the EFI variable store does not result in surprises.
Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
|