• <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久久精品66| 久久精品国产福利国产秒| 欧美亚洲另类久久综合| 久久久久国产精品麻豆AR影院| 亚洲精品国产字幕久久不卡| 精品一区二区久久| 久久精品桃花综合| 久久99热国产这有精品| 久久婷婷国产剧情内射白浆| 久久91精品国产91久久户| 久久久久国色AV免费看图片| 久久久久99精品成人片欧美| 无码8090精品久久一区| A级毛片无码久久精品免费| 久久亚洲AV成人无码国产| 精品久久久久久无码免费| 久久久久人妻一区二区三区vr| 久久综合久久鬼色| 亚洲午夜久久久精品影院 | 国产精品久久久久久福利漫画| 色婷婷久久久SWAG精品| 女人香蕉久久**毛片精品| 久久国产精品无码HDAV| 久久AV无码精品人妻糸列| 亚洲国产精品一区二区三区久久 | 久久婷婷国产麻豆91天堂| 偷窥少妇久久久久久久久| 久久中文字幕无码专区| 国产精自产拍久久久久久蜜| 99久久精品国产免看国产一区| 欧洲精品久久久av无码电影| 色播久久人人爽人人爽人人片AV | 久久久久亚洲精品无码蜜桃 | A级毛片无码久久精品免费| 合区精品久久久中文字幕一区| 日韩电影久久久被窝网| 亚洲国产天堂久久久久久| 色婷婷久久综合中文久久一本| 亚洲国产成人久久综合区| 99久久综合国产精品免费|