WDF_DRIVER_CONFIG - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// wdfdriver.h
typedef struct _WDF_DRIVER_CONFIG {
ULONG Size;
PFN_WDF_DRIVER_DEVICE_ADD EvtDriverDeviceAdd;
PFN_WDF_DRIVER_UNLOAD EvtDriverUnload;
ULONG DriverInitFlags;
ULONG DriverPoolTag;
} WDF_DRIVER_CONFIG, *PWDF_DRIVER_CONFIG;
View the official Windows Driver Kit DDI referenceNo description available.
[Applies to KMDF and UMDF]
The WDF_DRIVER_CONFIG structure is an input parameter to WdfDriverCreate.
SizeThe size, in bytes, of this structure.
EvtDriverDeviceAddA pointer to a driver's EvtDriverDeviceAdd callback function.
EvtDriverUnloadA pointer to a driver's EvtDriverUnload callback function.
DriverInitFlagsA bitwise OR of one or more WDF_DRIVER_INIT_FLAGS-typed values that identify driver initialization flags.
DriverPoolTag(KMDF versions 1.5 and later.) A driver-defined pool tag that the framework will assign to all of the driver's pool allocations. Debuggers display this tag. For more information about specifying a pool tag, see the following Remarks section.
Your driver can optionally specify a pool tag that the framework will assign to all of the driver's pool allocations. Drivers typically specify a character string of up to four characters, delimited by single quotation marks, in reverse order (for example, 'dcba'). The ASCII value of each character in the tag must be between 0 and 127.
If DriverPoolTag is zero, the framework creates a default pool tag by using the first four characters of your driver's kernel-mode service name. If the service name begins with "WDF" (the name is not case sensitive and does not include the quotation marks), the next four characters are used. If fewer than four characters are available, "FxDr" is used.
To initialize a WDF_DRIVER_CONFIG structure, drivers must call WDF_DRIVER_CONFIG_INIT.