• <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]WDK WMILIB_CONTEXT

            WMILIB_CONTEXT

            驅動數據塊和事件塊的注冊信息,驅動WMI庫回調例程的入口點
            The WMILIB_CONTEXT structure provides registration information for a driver's data blocks and event blocks and defines entry points for the driver's WMI library callback routines.

            typedef struct _WMILIB_CONTEXT {
              ULONG  GuidCount;
              PWMIGUIDREGINFO  GuidCount;
              PWMIGUIDREGINFO  GuidCount;
              PWMIGUIDREGINFO  GuidList;
              PWMI_QUERY_REGINFO  GuidList;
              PWMI_QUERY_REGINFO  QueryWmiRegInfo;
              PWMI_QUERY_DATABLOCK  QueryWmiRegInfo;
              PWMI_QUERY_DATABLOCK  QueryWmiDataBlock;
              PWMI_SET_DATABLOCK  QueryWmiDataBlock;
              PWMI_SET_DATABLOCK  SetWmiDataBlock;
              PWMI_SET_DATAITEM  SetWmiDataBlock;
              PWMI_SET_DATAITEM  SetWmiDataItem;
              PWMI_EXECUTE_METHOD  SetWmiDataItem;
              PWMI_EXECUTE_METHOD  ExecuteWmiMethod;
              PWMI_FUNCTION_CONTROL  ExecuteWmiMethod;
              PWMI_FUNCTION_CONTROL  WmiFunctionControl;
            } WMILIB_CONTEXT, *PWMILIB_CONTEXT;

            Members

            GuidCount
            Specifies the number of blocks registered by the driver.
            GuidList
            Pointer to an array of GuidCount WMIGUIDREGINFO structures that contain registration information for each block.
            QueryWmiRegInfo
            Pointer to the driver's DpWmiQueryReginfo routine, which is a required entry point for drivers that call WMI library support routines.
            QueryWmiDataBlock
            Pointer to the driver's DpWmiQueryDataBlock routine, which is a required entry point for drivers that call WMI library support routines.
            SetWmiDataBlock
            Pointer to the driver's DpWmiSetDataBlock routine, which is an optional entry point for drivers that call WMI library support routines. If the driver does not implement this routine, it must set this member to NULL. In this case, WMI returns STATUS_WMI_READ_ONLY to the caller in response to any IRP_MN_CHANGE_SINGLE_INSTANCE request.
            SetWmiDataItem
            Pointer to the driver's DpWmiSetDataItem routine, which is an optional entry point for drivers that call WMI library support routines. If the driver does not implement this routine, it must set this member to NULL. In this case, WMI returns STATUS_WMI_READ_ONLY to the caller in response to any IRP_MN_CHANGE_SINGLE_ITEM request.
            ExecuteWmiMethod
            Pointer to the driver's DpWmiExecuteMethod routine, which is an optional entry point for drivers that call WMI library support routines. If the driver does not implement this routine, it must set this member to NULL. In this case, WMI returns STATUS_INVALID_DEVICE_REQUEST to the caller in response to any IRP_MN_EXECUTE_METHOD request.
            WmiFunctionControl
            Pointer to the driver's DpWmiFunctionControl routine, which is an optional entry point for drivers that call WMI library support routines. If the driver does not implement this routine, it must set this member to NULL. In this case, WMI returns STATUS_SUCCESS to the caller in response to any IRP_MN_ENABLE_XXX or IRP_MN_DISABLE_XXX request.

            Comments

            A driver that handles WMI IRPs by calling WMI library support routines stores an initialized WMILIB_CONTEXT structure (or a pointer to such a structure) in its device extension. A driver can use the same WMILIB_CONTEXT structure for multiple device objects if each device object supplies the same set of data blocks.

            When the driver receives an IRP_MJ_SYSTEM_CONTROL request, it calls WmiSystemControl with a pointer to its WMILIB_CONTEXT structure, a pointer to its device object, and a pointer to the IRP. WmiSystemControl determines whether the IRP contains a WMI request and, if so, handles the request by calling the driver's appropriate DpWmiXxx routine.

            Memory for this structure can be allocated from paged pool.

            Requirements

            Headers: Defined in Wmilib.h. Include Wmilib.h.

            See Also

            DpWmiExecuteMethod, DpWmiFunctionControl, DpWmiQueryReginfo, DpWmiQueryDataBlock, DpWmiSetDataBlock, DpWmiSetDataItem, WMIGUIDREGINFO, WmiSystemControl

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

            導航

            統計

            留言簿(13)

            隨筆分類(287)

            隨筆檔案(289)

            漏洞

            搜索

            積分與排名

            最新評論

            閱讀排行榜

            青青热久久综合网伊人| 亚洲国产精品无码成人片久久| 久久青青草视频| 久久精品综合网| 无码人妻久久一区二区三区免费丨| 久久婷婷人人澡人人爽人人爱| 国产亚洲婷婷香蕉久久精品| 亚洲国产精品成人久久蜜臀 | 精品熟女少妇aⅴ免费久久| 国产成人综合久久精品红| 久久精品国产99国产电影网| 久久久久亚洲AV成人网| 国产免费久久精品丫丫| 91久久精一区二区三区大全| 久久人做人爽一区二区三区| 久久99国产精品99久久| 久久无码中文字幕东京热| 亚洲国产精品人久久| 免费观看久久精彩视频| 国产精品久久久香蕉| 国产精品欧美久久久久天天影视| 午夜不卡久久精品无码免费| 伊人久久五月天| 伊人久久大香线蕉成人| 久久久久亚洲av成人无码电影| 美女写真久久影院| 亚洲国产二区三区久久| 国产欧美一区二区久久| 久久久无码精品亚洲日韩按摩| 国产精品美女久久久久久2018| 国产精品久久国产精品99盘 | 久久综合成人网| 国产激情久久久久影院老熟女免费| 久久99精品久久久久婷婷| 无码人妻精品一区二区三区久久 | 久久国产乱子精品免费女| 久久精品99久久香蕉国产色戒 | 99久久精品无码一区二区毛片| 久久精品人人做人人爽电影| 久久91综合国产91久久精品| 韩国无遮挡三级久久|