• <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)

            漏洞

            搜索

            積分與排名

            最新評論

            閱讀排行榜

            武侠古典久久婷婷狼人伊人| 国产精品视频久久| 久久婷婷色综合一区二区| 狠狠色婷婷久久综合频道日韩| 久久精品亚洲精品国产色婷| 久久91精品综合国产首页| 久久精品国产久精国产果冻传媒| 2021久久国自产拍精品| 亚洲精品综合久久| 青青青青久久精品国产h| 一本久道久久综合狠狠爱| 99久久www免费人成精品| 亚洲精品乱码久久久久久 | 色偷偷888欧美精品久久久| 色诱久久av| 久久97久久97精品免视看秋霞| 亚洲精品乱码久久久久久按摩 | 亚洲狠狠婷婷综合久久久久| 91精品久久久久久无码| 97久久超碰国产精品旧版| 久久这里都是精品| 亚洲精品NV久久久久久久久久| 久久免费精品一区二区| 久久久一本精品99久久精品88| 国产美女亚洲精品久久久综合| 久久这里只有精品视频99| 午夜不卡888久久| 91久久国产视频| 99久久精品费精品国产| 伊人久久综合热线大杳蕉下载| 久久精品蜜芽亚洲国产AV| 久久精品国产亚洲AV麻豆网站| 亚洲国产精品久久电影欧美| 日日躁夜夜躁狠狠久久AV| 亚洲中文字幕无码久久2017| 老男人久久青草av高清| 久久精品国产亚洲AV蜜臀色欲| 久久人人爽人人爽人人片av麻烦| 久久精品国产色蜜蜜麻豆| 熟妇人妻久久中文字幕| 久久久久亚洲Av无码专|