On Thu, 26 Nov, at 01:06:27PM, Ard Biesheuvel wrote: > > How would this be affected by things like suspend/resume, hibernation > or variable accesses made in SMM context (i.e., which the kernel knows > nothing about) > If we need to take all of that into account as well, we're probably > better off adding a nonblocking query_variable_info() call after all, > and wiring it up to efi_query_variable_store(), i.e., make it take a > 'bool nonblocking' argument and choose between the two versions of > each of the hooks it uses. I *think* that'd be OK. The thing I wanted to avoid was a proliferation of nonblocking versions of the standard EFI calls, but limiting it to adding query_variable_info() doesn't seem too bad. Let me think about it over the weekend. -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
