Expand Minimize

KeRegisterProcessorChangeCallback routine

The KeRegisterProcessorChangeCallback routine registers a callback function with the operating system so that the operating system will notify the driver when a new processor is added to the hardware partition.

Syntax


PVOID KeRegisterProcessorChangeCallback(
  _In_      PPROCESSOR_CALLBACK_FUNCTION CallbackFunction,
  _In_opt_  PVOID CallbackContext,
  _In_      ULONG Flags
);

Parameters

CallbackFunction [in]

A pointer to a driver-supplied processor change callback function that is to be called by the operating system whenever a new processor is added to the hardware partition. A processor change callback function is defined as follows:


VOID
  ProcessorCallback(
    __in PVOID CallbackContext,
    __in PKE_PROCESSOR_CHANGE_NOTIFY_CONTEXT ChangeContext,
    __inout PNTSTATUS OperationStatus
    );

CallbackContext

The context that was supplied in the CallbackContext parameter to the KeRegisterProcessorChangeCallback routine when the callback function was registered with the operating system.

ChangeContext

A pointer to a KE_PROCESSOR_CHANGE_NOTIFY_CONTEXT structure that describes the processor change notification event.

OperationStatus

A pointer to a variable that contains an NTSTATUS code. A device driver must not change the value of this variable except if an error occurs during the processing of the callback function when the State member of the KE_PROCESSOR_CHANGE_NOTIFY_CONTEXT structure that is pointed to by the ChangeContext parameter contains KeProcessorAddStartNotify.

The processor change callback function is called at IRQL = PASSIVE_LEVEL.

CallbackContext [in, optional]

A driver-supplied context that is passed to the callback function. This parameter can be NULL.

Flags [in]

Optional flags that modify the behavior of the KeRegisterProcessorChangeCallback routine. The following is one possible flag:

KE_PROCESSOR_CHANGE_ADD_EXISTING

If this flag is set, the registered callback function is immediately called for each active processor that currently exists in the hardware partition, in addition to being called whenever a new processor is added to the hardware partition. If this flag is not set, the registered callback function is only called whenever a new processor is added to the system.

Return value

KeRegisterProcessorChangeCallback returns a non-NULL callback registration handle if the callback function is successfully registered with the operating system. Otherwise, KeRegisterProcessorChangeCallback returns NULL. For more information about this handle, see the following Remarks section.

Remarks

A device driver calls the KeRegisterProcessorChangeCallback routine to register a callback function that is to be called by the operating system whenever a new processor is added to the hardware partition. When a user hot-plugs a new processor into the partition, the operating system calls the registered callback functions to rebalance the system resources that are allocated among the processors in the partition.

The registered callback function is called two times whenever a new processor is added to the hardware partition. The first time that the callback function is called, the State member of the KE_PROCESSOR_CHANGE_NOTIFY_CONTEXT structure that is pointed to by the ChangeContext parameter contains KeProcessorAddStartNotify. It is during this callback that the device driver should allocate any per-processor resources and perform any other tasks in preparation for the new processor to become active in the hardware partition. If an error occurs while the device driver processes this callback that could cause a bugcheck to occur if the operating system continues to add the new processor to the hardware partition, the callback function sets the variable that is pointed to by the OperationStatus parameter to an NTSTATUS code that describes the error condition. For example, if the device driver experiences a memory allocation failure for a per-processor data structure for a new processor, the callback function sets this variable to STATUS_INSUFFICIENT_RESOURCES. If the callback is processed successfully, the contents of the variable that is pointed to by the OperationStatus parameter should not be changed.

The second time that the callback function is called, the State member of the KE_PROCESSOR_CHANGE_NOTIFY_CONTEXT structure that is pointed to by the ChangeContext parameter contains either KeProcessorAddCompleteNotify, which indicates that the operating system has added the new processor to the hardware partition successfully, or KeProcessorAddFailureNotify, which indicates that the operating system did not add the new processor to the hardware partition. If the operating system successfully adds the new processor to the hardware partition, the callback function is not called the second time until after the new processor has been started and is available for thread scheduling. If the operating system did not add the new processor to the hardware partition, the device driver should free any per-processor resources during the second callback that it allocated during the first callback.

If the device driver specifies the KE_PROCESSOR_CHANGE_ADD_EXISTING flag in the Flags parameter when it calls the KeRegisterProcessorChangeCallback routine, the callback function is immediately called one time for each active processor that currently exists in the hardware partition. For these callbacks, the State member of the KE_PROCESSOR_CHANGE_NOTIFY_CONTEXT structure that is pointed to by the ChangeContext parameter contains KeProcessorAddStartNotify. It is during these callbacks that the device driver should allocate any per-processor resources and perform any other tasks to prepare to use the existing processors in the hardware partition. If the device driver successfully processes this callback for all active processors that currently exist in the hardware partition, the callback function is immediately called again for each active processor that currently exists in the hardware partition. For these callbacks, the State member of the KE_PROCESSOR_CHANGE_NOTIFY_CONTEXT structure that is pointed to by the ChangeContext parameter contains KeProcessorAddCompleteNotify. KeRegisterProcessorChangeCallback returns after these callbacks complete.

If an error occurs while the device driver processes the first callback for one of the existing active processors in the hardware partition that could cause a bugcheck to occur if the driver were to continue to load, the callback function sets the variable pointed to by the OperationStatus parameter to an NTSTATUS code that describes the error condition. For example, if the device driver experiences a memory allocation failure for a per-processor data structure for an existing active processor, the callback function sets this variable to STATUS_INSUFFICIENT_RESOURCES. If the callback is processed successfully, the contents of the variable that is pointed to by the OperationStatus parameter should not be changed.

If the device driver indicates an error when the first callback for one of the existing active processors in the hardware partition is processed, the callback function is not called for any more of the existing active processors. Instead, the callback function is immediately called a second time for each active processor for which the callback was called the first time, excluding the active processor for which the callback indicated the error. For these callbacks, the State member of the KE_PROCESSOR_CHANGE_NOTIFY_CONTEXT structure that is pointed to by the ChangeContext parameter contains KeProcessorAddFailureNotify.

A device driver typically calls the KeRegisterProcessorChangeCallback routine from within its DriverEntry routine. If the call to the KeRegisterProcessorChangeCallback routine returns NULL, the device driver's DriverEntry routine should return an NTSTATUS code that describes the error condition.

Note   A device driver can use the context that is passed in the CallbackContext parameter to the KeRegisterProcessorChangeCallback routine as a place where the callback function can store the NTSTATUS code that describes the error condition. This NTSTATUS code can then be used as the return value for the device driver's DriverEntry routine.

Note  The status value returned by KeRegisterProcessorChangeCallback indicates only whether the registration of the callback function succeeds or fails. It does not indicate the success or failure of any calls to callback functions that might occur before KeRegisterProcessorChangeCallback returns.

A callback function that has been registered for notification of processor changes must be unregistered before the device driver is unloaded from the operating system. To unregister the callback function, the device driver calls the KeDeregisterProcessorChangeCallback routine, and passes, as an input parameter to this routine, the registration handle that was returned by the call to the KeRegisterProcessorChangeCallback routine.

Requirements

Version

Available in Windows Server 2008 and later versions of Windows.

Header

Wdm.h (include Wdm.h, Ntddk.h, or Ntifs.h)

Library

Ntoskrnl.lib

IRQL

PASSIVE_LEVEL

See also

KeDeregisterProcessorChangeCallback
KE_PROCESSOR_CHANGE_NOTIFY_CONTEXT

 

 

Send comments about this topic to Microsoft

Show:
© 2014 Microsoft