• <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 小默 閱讀(475) 評論(0)  編輯 收藏 引用 所屬分類: Windows

            導航

            統計

            留言簿(13)

            隨筆分類(287)

            隨筆檔案(289)

            漏洞

            搜索

            積分與排名

            最新評論

            閱讀排行榜

            2020久久精品亚洲热综合一本| 久久国产成人精品麻豆| 欧美久久亚洲精品| 久久综合亚洲色HEZYO国产| 久久人人爽人人人人片av| 欧美丰满熟妇BBB久久久| 国产成人久久精品区一区二区| 久久无码人妻精品一区二区三区| 久久精品国产亚洲AV香蕉| 婷婷久久综合九色综合98| 久久综合久久性久99毛片| 久久亚洲欧美国产精品| 性高湖久久久久久久久AAAAA| 久久婷婷五月综合色奶水99啪 | 久久WWW免费人成一看片| 国产精品久久久久久久| 久久久久久精品免费看SSS | 久久天天躁夜夜躁狠狠躁2022| 996久久国产精品线观看| 老男人久久青草av高清| 久久久91人妻无码精品蜜桃HD| 精品一区二区久久| 精品久久无码中文字幕| 午夜天堂精品久久久久| 久久受www免费人成_看片中文| 91精品国产91久久久久久蜜臀| 久久综合香蕉国产蜜臀AV| 亚洲中文字幕久久精品无码喷水| 午夜福利91久久福利| 日批日出水久久亚洲精品tv| 久久免费视频观看| 久久99国产精品久久99| 国产精品久久久久久久久免费| 好久久免费视频高清| 国产精品视频久久| 天天久久狠狠色综合| Xx性欧美肥妇精品久久久久久| 久久99热国产这有精品| 伊人久久综在合线亚洲2019| 91精品国产综合久久香蕉| 狠狠色丁香婷婷综合久久来来去 |