class EfiBootShim

Initialize the shim items using the UEFI System Table. This

initializes all the standard item types from EfiBootShimBase.

Each of Items... may have one of these methods:

* void Init(efi_system_table* systab, const char* shim_name, FILE* log);

* fit::result

<efi

_status> Init(efi_system_table* systab,

const char* shim_name, FILE* log);

* fit::result

<Error

> Init(efi_system_table* systab,

const char* shim_name, FILE* log);

Each item that does will have its method called here. The caller of this

Init() method is responsible for initializing any items that use different

Init() signatures.

If Init() found ACPI tables via the UEFI tables, this will be set.

This manages the entire loading and booting sequence via callbacks.

It only returns for error cases.

First, it loads and split the input ZBI and prepare the data ZBI with shim

items. The load function is called with the extra data capacity to leave

in the DataZbi for shim items. It may be called multiple times if the

capacity has to be increased. It should return the DataZbi container

loaded from the input ZBI with at least that much capacity remaining.

This will then append all the shim items, and call ExitBootServices()

immediately after calling last_chance(). This is final opportunity to use

UEFI Boot Services and prevent booting; it's the place for final logging.

After ExitBootServices succeeds, boot(zbi) is called with the final

location of the data ZBI, and must not return. It should immediately boot

into the new kernel without doing anything that might attempt to use UEFI

calls. (This is why it's done via callback rather than returning to the

caller, where many destructors would ordinarily run.)

This manages the entire loading and booting sequence via callbacks.

It only returns for error cases.

First, it loads and split the input ZBI and prepare the data ZBI with shim

items. The load function is called with the extra data capacity to leave

in the DataZbi for shim items. It may be called multiple times if the

capacity has to be increased. It should return the DataZbi container

loaded from the input ZBI with at least that much capacity remaining.

This will then append all the shim items, and call ExitBootServices()

immediately after calling last_chance(). This is final opportunity to use

UEFI Boot Services and prevent booting; it's the place for final logging.

After ExitBootServices succeeds, boot(zbi) is called with the final

location of the data ZBI, and must not return. It should immediately boot

into the new kernel without doing anything that might attempt to use UEFI

calls. (This is why it's done via callback rather than returning to the

caller, where many destructors would ordinarily run.)

This manages the entire loading and booting sequence via callbacks.

It only returns for error cases.

First, it loads and split the input ZBI and prepare the data ZBI with shim

items. The load function is called with the extra data capacity to leave

in the DataZbi for shim items. It may be called multiple times if the

capacity has to be increased. It should return the DataZbi container

loaded from the input ZBI with at least that much capacity remaining.

This will then append all the shim items, and call ExitBootServices()

immediately after calling last_chance(). This is final opportunity to use

UEFI Boot Services and prevent booting; it's the place for final logging.

After ExitBootServices succeeds, boot(zbi) is called with the final

location of the data ZBI, and must not return. It should immediately boot

into the new kernel without doing anything that might attempt to use UEFI

calls. (This is why it's done via callback rather than returning to the

caller, where many destructors would ordinarily run.)

This manages the entire loading and booting sequence via callbacks.

It only returns for error cases.

First, it loads and split the input ZBI and prepare the data ZBI with shim

items. The load function is called with the extra data capacity to leave

in the DataZbi for shim items. It may be called multiple times if the

capacity has to be increased. It should return the DataZbi container

loaded from the input ZBI with at least that much capacity remaining.

This will then append all the shim items, and call ExitBootServices()

immediately after calling last_chance(). This is final opportunity to use

UEFI Boot Services and prevent booting; it's the place for final logging.

After ExitBootServices succeeds, boot(zbi) is called with the final

location of the data ZBI, and must not return. It should immediately boot

into the new kernel without doing anything that might attempt to use UEFI

calls. (This is why it's done via callback rather than returning to the

caller, where many destructors would ordinarily run.)