Description

The Reinitialize routine continues driver and device initialization after the driver's DriverEntry routine returns.

Parameters

DriverObject [in]

Caller-supplied pointer to a DRIVER_OBJECT structure. This is the driver's driver object.

Context [in, optional]

Caller-supplied pointer to context information, specified in a previous call to IoRegisterDriverReinitialization or IoRegisterBootDriverReinitialization.

Count [in]

Caller-supplied value representing the number of times the Reinitialize routine has been called, including the current call.

Remarks

To queue a Reinitialize routine for execution, a driver's DriverEntry routine must call either IoRegisterDriverReinitialization or IoRegisterBootDriverReinitialization. The Reinitialize routine can also call IoRegisterDriverReinitialization itself, which causes the routine to be requeued. This requeuing can occur multiple times, and the routine's Count parameter indicates the number of times it has been called. The first call to IoRegisterDriverReinitialization must be made from DriverEntry, and DriverEntry must return STATUS_SUCCESS.

For more information about implementing a Reinitialize routine, see Writing a Reinitialize Routine.

Examples

To define a Reinitialize callback routine, you must first provide a function declaration that identifies the type of callback routine you're defining. Windows provides a set of callback function types for drivers. Declaring a function using the callback function types helps Code Analysis for Drivers, Static Driver Verifier (SDV), and other verification tools find errors, and it's a requirement for writing drivers for the Windows operating system.

For example, to define a Reinitialize callback routine that is named MyReinitialize, use the DRIVER_REINITIALIZE type as shown in this code example:

DRIVER_REINITIALIZE MyReinitialize;

Then, implement your callback routine as follows:

_Use_decl_annotations_
VOID
  MyReinitialize(
    struct _DRIVER_OBJECT  *DriverObject,
    PVOID  Context,
    ULONG  Count
    )
  {
      // Function body
  }

The DRIVER_REINITIALIZE function type is defined in the Wdm.h header file. To more accurately identify errors when you run the code analysis tools, be sure to add the _Use_decl_annotations_ annotation to your function definition. The _Use_decl_annotations_ annotation ensures that the annotations that are applied to the DRIVER_REINITIALIZE function type in the header file are used. For more information about the requirements for function declarations, see Declaring Functions by Using Function Role Types for WDM Drivers. For information about _Use_decl_annotations_, see Annotating Function Behavior.