Intel Extensible Firmware Interface Specification page 50

Extensible Firmware Interface Specification
can't clean up on behalf of drivers that have been loaded into the system. The drivers have to do
that themselves by creating an event whose type is
whose notification function is a function within the driver itself. Then, when
ExitBootServices()
EVT_SIGNAL_EXIT_BOOT_SERVICES.
Another example of the use of synchronous events occurs when an event of type
EVT_SIGNAL_VIRTUAL_ADDRESS_CHANGE
SetVirtualAddressmap()
The
EVT_NOTIFY_WAIT
specified, the caller does not require any notification concerning the event and the NotifyTpl,
NotifyFunction, and
specified, then the event is signaled and its notify function is queued whenever a consumer of the
event is waiting for it (via
EVT_NOTIFY_SIGNAL
event is signaled.
Note: Since its internal structure is unknown to the caller,
The only way to manipulate it is to use the published event interfaces.
Status Codes Returned
EFI_SUCCESS
EFI_INVALID_PARAMETER
EFI_OUT_OF_RESOURCES
32
EVT_SIGNAL_EXIT_BOOT_SERVICES
has finished its cleanup, it signals each event of type
is used in conjunction with the
function. For more information, see Section 3.7.1.
and
EVT_NOTIFY_SIGNAL
parameters are ignored. If
NotifyContext
or CheckEvent()). If the
WaitForEvent()
flag is specified then the event's notify function is queued whenever the
The event structure was created.
One of the parameters has an invalid value.
The event could not be allocated.
12/12/00
flags are exclusive. If neither flag is
EVT_NOTIFY_WAIT
cannot be modified by the caller.
Event
Version 1.02
and
is