On 12 July 2018 at 15:12, Mark Brown broonie@kernel.org wrote:
On Thu, Jul 12, 2018 at 01:50:45PM +0100, Daniel Thompson wrote:
The OS will discover the variable is non-modifiable when it tried to set it. Won't the current proposal mislead standards compliant use of GetVariable()? For example does it it makes standards compliant code *more* likely to call SetVariable() in order to fix up a variable that it thinks was incorrectly set with the NON_VOLATILE attribute.
Do any existing implementations change variables from non-volatile to volatile?
The UEFI spec is explicit about which variables are volatile and which are not. Simply relaxing non-volatile to volatile in the general case doesn't seem like a useful approach to me.
Hi Ard
Do any existing implementations change variables from non-volatile to volatile?
The UEFI spec is explicit about which variables are volatile and which are not. Simply relaxing non-volatile to volatile in the general case doesn't seem like a useful approach to me.
I believe at boot-time, UEFI specs will be followed for volatile and non-volatile variables. Having this in statement EBBR, will help those platform, which cannot expose non-volatile variables at runtime.
Regards Udit
boot-architecture@lists.linaro.org
-
Ard Biesheuvel -
Udit Kumar