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

            導航

            統計

            留言簿(13)

            隨筆分類(287)

            隨筆檔案(289)

            漏洞

            搜索

            積分與排名

            最新評論

            閱讀排行榜

            伊人久久综合成人网| 亚洲Av无码国产情品久久| 无遮挡粉嫩小泬久久久久久久| 久久www免费人成看片| 一本色道久久99一综合| 久久亚洲日韩精品一区二区三区| 久久久国产精品亚洲一区| 999久久久国产精品| 精品国产乱码久久久久久人妻| 久久亚洲精精品中文字幕| 国产—久久香蕉国产线看观看| 久久午夜夜伦鲁鲁片免费无码影视| 久久国产亚洲精品无码| 人人狠狠综合88综合久久| 99久久久国产精品免费无卡顿 | 久久亚洲国产成人影院| 久久久久人妻一区二区三区vr| 久久国产精品国语对白| 亚洲中文字幕久久精品无码喷水| 一本久久久久久久| 97久久久精品综合88久久| 中文字幕精品无码久久久久久3D日动漫 | 久久久久久亚洲精品无码| 国内精品久久久人妻中文字幕| 精品无码久久久久久久久久| 国产精品无码久久久久久| 香蕉久久久久久狠狠色| 久久av免费天堂小草播放| 国产精品久久精品| 国产∨亚洲V天堂无码久久久| 久久精品国产男包| 中文国产成人精品久久亚洲精品AⅤ无码精品| 99精品国产在热久久无毒不卡| 亚洲精品乱码久久久久久久久久久久| 久久综合狠狠综合久久激情 | 亚洲乱码精品久久久久..| 亚洲精品国产综合久久一线| 久久国产视频99电影| 国产毛片久久久久久国产毛片 | 国产2021久久精品| 色综合久久88色综合天天|