• <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>

            小默

            [zz]DispatchPnP

            DispatchPnP

            The DispatchPnP routine services IRPs containing the IRP_MJ_PNP I/O function code.

            DRIVER_DISPATCH DispatchPnP;

            NTSTATUS
              DispatchPnP(
                __in struct _DEVICE_OBJECT  *DeviceObject,
                __in struct _IRP  *Irp
                )
              {...}

            Parameters

            DeviceObject
            Caller-supplied pointer to a DEVICE_OBJECT structure. This is the device object for the target device, previously created by the driver's AddDevice routine.
            Irp
            Caller-supplied pointer to an IRP structure that describes the requested I/O operation.

            Return Value

            If the routine succeeds, it must return STATUS_SUCCESS. Otherwise, it must return one of the error status values defined in Ntstatus.h.

            Comments

            A driver's DispatchPnP routine should be named XxxDispatchPnP, where Xxx is a driver-specific prefix. The driver's DriverEntry routine must store the DispatchPnP routine's address in DriverObject->MajorFunction[IRP_MJ_PNP].

            Input parameters for all Dispatch routines are supplied in the IRP structure pointed to by Irp. Additional parameters are supplied in the driver's associated I/O stack location, which is described by the IO_STACK_LOCATION structure and can be obtained by calling IoGetCurrentIrpStackLocation.

            Generally, all Dispatch routines execute in an arbitrary thread context at IRQL = PASSIVE_LEVEL, but there are exceptions. For more information, see Dispatch Routines and IRQLs.

            For more information about DispatchPnP routines, see Writing Dispatch Routines. For more information about IRPs, see Handling IRPs.

            Example

            To define a DispatchPnP callback function that is named MyDispatchPnP, you must first provide a function declaration that Static Driver Verifier (SDV) and other verification tools require, as follows:

            DRIVER_DISPATCH MyDispatchPnP;

             

            Then, implement your callback function as follows:

            NTSTATUS
              MyDispatchPnP(
                __in struct _DEVICE_OBJECT  *DeviceObject,
                __in struct _IRP  *Irp
                )
              {
                  // Function body
              }

             

            The DRIVER_DISPATCH function type is defined in the Wdm.h header file. For more information about SDV requirements for function declarations, see Declaring Functions Using Function Role Types for WDM Drivers.

            Requirements

            IRQL: PASSIVE_LEVEL (see Comments section)

            Headers: Declared in Wdm.h. Include Wdm.h, Ntddk.h, or Ntifs.h.

            posted on 2009-12-29 11:20 小默 閱讀(273) 評論(0)  編輯 收藏 引用 所屬分類: Windows

            導航

            統計

            留言簿(13)

            隨筆分類(287)

            隨筆檔案(289)

            漏洞

            搜索

            積分與排名

            最新評論

            閱讀排行榜

            久久夜色精品国产亚洲| 99久久久久| 亚洲级αV无码毛片久久精品| 亚洲午夜久久久久久噜噜噜| 国产精品久久久久jk制服| 99999久久久久久亚洲| 99久久精品免费看国产免费| 色偷偷91久久综合噜噜噜噜| 久久久精品国产sm调教网站 | 久久九色综合九色99伊人| 久久国产免费直播| 麻豆精品久久精品色综合| 久久久无码精品亚洲日韩京东传媒 | 久久精品中文字幕有码| 久久精品无码专区免费东京热| 色成年激情久久综合| 久久成人国产精品免费软件| 久久精品国产72国产精福利| 大伊人青草狠狠久久| 精品久久久无码21p发布| 久久久久久极精品久久久| 国产精品久久久久…| 女人高潮久久久叫人喷水| 国产A级毛片久久久精品毛片| 亚洲色大成网站www久久九| 久久亚洲高清综合| 久久免费精品一区二区| 久久综合88熟人妻| 久久精品中文无码资源站| 亚洲欧美日韩中文久久| 久久人人爽人人人人片av| 久久这里都是精品| 亚洲国产精品无码久久久久久曰 | 性高湖久久久久久久久AAAAA| 国产亚洲精午夜久久久久久| 青青青青久久精品国产| 国产福利电影一区二区三区,免费久久久久久久精 | 久久强奷乱码老熟女| 国产精品欧美久久久久无广告| AV无码久久久久不卡网站下载| 日产精品99久久久久久|