On Thu, 30 May 2013, Russ Anderson wrote:
> > > > > Yes, but this call is clearly happening way before ExitBootServices() --
> > > > > see the surrounding code, see for example this in efi_main():
> > > > >
> > > > > [ ... snip ... ]
> > > > > setup_efi_vars(boot_params);
> > > > >
> > > > > setup_efi_pci(boot_params);
> > > > >
> > > > > status = efi_call_phys3(sys_table->boottime->allocate_pool,
> > > > > EFI_LOADER_DATA, sizeof(*gdt),
> > > > > (void **)&gdt);
> > > > > if (status != EFI_SUCCESS) {
> > > > > efi_printk("Failed to alloc mem for gdt structure\n");
> > > > > goto fail;
> > > > > }
> > > > > [ ... snip ... ]
> > > >
> > > > Yes. Note the failing call is sys_table->runtime while all the
> > > > other calls are sys_table->boottime and seem to work. Not sure
> > > > why the sys_table->runtime call has a problem but it may be
> > > > a clue. Could something in the runtime path not be set up???
> > >
> > > That was my original idea early today as well. My understanding of the
> > > UEFI spec is admittedly limited, but afaics calling runtime method from
> > > boot environment should be a valid thing to do ... ?
> >
> > QueryVariableInfo() is a runtime services, all runtime services should
> > available bother on boot time and runtime:
> >
> > UEFI spec 2.3.1 P.109:
> > Runtime Services
> > Functions that are available before and after any call to
> > ExitBootServices(). These functions are described in Section 7.
>
> That's a great idea. This patch moves the QueryVariableInfo()
> call from bootime to runtime, in efi_late_init(). The attached
> patch is consistent with the UEFI spec and avoids the problem.
Unfortunately that means that you can as well throw the patch away
completely.
The sole point is to run the QueryVariableInfo() from the boot
environment, in order to obtain more accurate information.
And it's a valid thing to do, according to UEFI specification.
--
Jiri Kosina
SUSE Labs
--
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
