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

            漏洞

            搜索

            積分與排名

            最新評論

            閱讀排行榜

            久久影院久久香蕉国产线看观看| 色成年激情久久综合| 一本色道久久88加勒比—综合| 久久国产乱子伦精品免费午夜| 一级a性色生活片久久无少妇一级婬片免费放 | 69久久夜色精品国产69| 狠狠久久综合伊人不卡| 97精品国产91久久久久久| 天天爽天天爽天天片a久久网| 香蕉久久永久视频| 久久久久久青草大香综合精品| 久久亚洲国产精品五月天婷| 亚洲va中文字幕无码久久不卡 | 久久香蕉一级毛片| 国内精品伊人久久久久777| 国产午夜福利精品久久| 99久久久国产精品免费无卡顿| 久久九九久精品国产免费直播| 久久久久99精品成人片三人毛片| 久久免费看黄a级毛片| 久久久久国产一区二区三区| 日本久久久久亚洲中字幕| 色综合久久久久综合体桃花网| 久久r热这里有精品视频| 久久综合丁香激情久久| 国产美女亚洲精品久久久综合| 国产午夜精品理论片久久| 色综合久久中文综合网| 久久A级毛片免费观看| 久久精品一区二区三区不卡| 波多野结衣久久一区二区| 欧洲成人午夜精品无码区久久 | 久久久久久久97| 一本综合久久国产二区| 亚洲天堂久久久| 色8久久人人97超碰香蕉987| 亚洲七七久久精品中文国产| 久久免费99精品国产自在现线 | 成人国内精品久久久久一区| 久久棈精品久久久久久噜噜| 久久天天躁狠狠躁夜夜avapp|