PFND3D12DDI_BEGIN_PASS - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// d3d12umddi.h
PFND3D12DDI_BEGIN_PASS Pfnd3d12ddiBeginPass;
VOID Pfnd3d12ddiBeginPass(
D3D12DDI_HCOMMANDLIST unnamedParam1,
D3D12DDI_HPASS unnamedParam2,
D3D12DDI_PASS_FLAGS PassFlags
)
{...}
View the official Windows Driver Kit DDI referenceNo description available.
The driver is notified that the app has started of a pass of consistent workloads. When the driver is notified that an app pass has started, the driver either records observations or uses optimizations that have been discovered.
unnamedParam1A handle to the driver's data for the command list. The driver uses this region of memory to store internal data structures that are related to its command list.
unnamedParam2A handle to the pass that was created by the app.
PassFlagsA flag to indicate what the driver should do when an app starts a pass.
//Declaration
PFND3D12DDI_BEGIN_PASS Pfnd3d12ddiBeginPass;
// Definition
VOID Pfnd3d12ddiBeginPass
(
D3D12DDI_HCOMMANDLIST Arg1
D3D12DDI_HPASS Arg2
D3D12DDI_PASS_FLAGS PassFlags
)
{...}
This callback is used as part of a test to see if drivers can find perf wins from being told when apps are repeating "passes" of consistent workloads. The app instructs the driver to observe how some passes run and gives the driver a chance to make optimizations for future runs of the same pass. The contents of a "pass" can be anything - it is up to the app to be relatively consistent in the overall performance characteristics of a pass.