• <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高清免费毛片久久| 久久久亚洲欧洲日产国码二区 | 伊人 久久 精品| 999久久久国产精品| 中文字幕成人精品久久不卡| 久久亚洲精品成人AV| 久久久久国产精品熟女影院| 国产高清美女一级a毛片久久w| 久久久久久毛片免费看| 伊人久久大香线蕉综合影院首页| 久久免费精品视频| 精产国品久久一二三产区区别| 国产91色综合久久免费分享| 99久久综合国产精品免费| 国产午夜久久影院| 亚洲AV成人无码久久精品老人| 国产精品无码久久四虎| 亚洲国产精品无码久久久秋霞2| 91久久精品国产免费直播| 久久SE精品一区二区| 日本精品久久久久久久久免费| 久久91精品久久91综合| 中文字幕无码av激情不卡久久| 国产精品成人久久久久三级午夜电影 | 亚洲一区中文字幕久久| 亚洲AV日韩AV永久无码久久| 久久中文字幕人妻丝袜| 久久综合久久伊人| 久久久久国产精品嫩草影院 | 久久99精品国产麻豆蜜芽| 91精品国产色综合久久| MM131亚洲国产美女久久| 久久99热这里只有精品国产| 伊人久久国产免费观看视频| 思思久久好好热精品国产| 久久狠狠一本精品综合网| 91麻精品国产91久久久久| 91亚洲国产成人久久精品| 色噜噜狠狠先锋影音久久|