Skip to content

Latest commit

 

History

History
74 lines (60 loc) · 2.01 KB

nf-d3dkmthk-d3dkmtdestroydoorbell.md

File metadata and controls

74 lines (60 loc) · 2.01 KB
UID tech.root title ms.date targetos description prerelease req.assembly req.construct-type req.ddi-compliance req.dll req.header req.idl req.include-header req.irql req.kmdf-ver req.lib req.max-support req.namespace req.redist req.target-min-winverclnt req.target-min-winversvr req.target-type req.type-library req.umdf-ver req.unicode-ansi topic_type api_type api_location api_name f1_keywords dev_langs helpviewer_keywords
NF:d3dkmthk.D3DKMTDestroyDoorbell
display
D3DKMTDestroyDoorbell
05/22/2023
Windows
Learn more about the D3DKMTDestroyDoorbell function.
true
function
d3dkmthk.h
WIN11_FUTURE
apiref
DllExport
d3dkmthk.h
D3DKMTDestroyDoorbell
D3DKMTDestroyDoorbell
d3dkmthk/D3DKMTDestroyDoorbell
c++
D3DKMTDestroyDoorbell

-description

D3DKMTDestroyDoorbell destroys a doorbell object.

-parameters

-param unnamedParam1

[in] Pointer to a D3DKMT_DESTROY_DOORBELL structure that identifies the hardware queue whose doorbell is to be destroyed.

-returns

D3DKMTDestroyDoorbell returns STATUS_SUCCESS when the OS successfully destroys the doorbell object. If hDoorbell points to a valid doorbell, then this call always succeeds; otherwise it returns STATUS_INVALID_PARAMETER.

-remarks

When UMD calls D3DKMTDestroyDoorbell, the OS does the following:

  • Removes its reference to hRingBuffer and to hRingBufferControl allocations belonging to this doorbell.
  • Frees the mapping that pDoorbellStatusCPUVirtualAddress points to.
  • Frees both the user-mode and kernel-mode mappings that pDoorbellCPUVirtuslAddress points to.
  • Calls KMD's [DxgkDdiDestroyDoorbell] so that KMD can disconnect the physical doorbell location and destroy its doorbell objects.

The UMD must not use the handle after calling D3DKMTDestroyDoorbell.

-see-also

D3DKMT_DESTROY_DOORBELL

D3DKMTCreateDoorbell