news 2026/7/22 12:33:49

\_PIC.phGPIC的实现和ACPI!Method函数分析

作者头像

张小明

前端开发工程师

1.2k 24
文章封面图
\_PIC.phGPIC的实现和ACPI!Method函数分析


\_PIC.phGPIC的实现和ACPI!Method函数分析

第一部分：
0: kd> dx -id 0,0,899a2278 -r1 ((ACPI!_List *)0x899af394)
((ACPI!_List *)0x899af394) : 0x899af394 [Type: _List *]
[+0x000] plistPrev : 0x899af2d0 [Type: _List *]
[+0x004] plistNext : 0x899af3d8 [Type: _List *]
0: kd> db 0x899af3d8
899af3d8 94 f3 9a 89 68 f0 9a 89-24 f0 9a 89 00 00 00 00 ....h...$.......
899af3e8 5f 50 49 43 30 f3 9a 89-94 f3 9a 89 00 00 08 00 _PIC0...........
899af3f8 00 00 00 00 00 00 00 00-17 00 00 00 1c f4 9a 89 ................
899af408 00 00 00 00 00 00 00 00-48 4d 45 54 24 00 00 00 ........HMET$...
899af418 00 f0 9a 89 00 00 00 00-00 00 00 00 00 00 00 00 ................
899af428 00 00 00 00 01 70 68 47-50 49 43 00 48 4f 52 47 .....phGPIC.HORG
899af438 34 00 00 00 00 f0 9a 89-39 0e ab f7 84 00 00 00 4.......9.......
899af448 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................


0: kd> dt _nsobj 0x899af3d8
ACPI!_NSObj
+0x000 list : _List
+0x008 pnsParent : 0x899af024 _NSObj
+0x00c pnsFirstChild : (null)
+0x010 dwNameSeg : 0x4349505f
+0x014 hOwner : 0x899af330 Void
+0x018 pnsOwnedNext : 0x899af394 _NSObj
+0x01c ObjData : _ObjData
+0x030 Context : (null)
+0x034 dwRefCount : 0
0: kd> dx -id 0,0,899a2278 -r1 (*((ACPI!_ObjData *)0x899af3f4))
(*((ACPI!_ObjData *)0x899af3f4)) [Type: _ObjData]
[+0x000] dwfData : 0x0 [Type: unsigned short]
[+0x002] dwDataType : 0x8 [Type: unsigned short] OBJTYPE_METHOD=0x8
[+0x004] dwRefCount : 0x0 [Type: unsigned long]
[+0x004] pdataBase : 0x0 [Type: _ObjData *]
[+0x008] dwDataValue : 0x0 [Type: unsigned long]
[+0x008] uipDataValue : 0x0 [Type: unsigned long]
[+0x008] pnsAlias : 0x0 [Type: _NSObj *]
[+0x008] pdataAlias : 0x0 [Type: _ObjData *]
[+0x008] powner : 0x0 [Type: void *]
[+0x00c] dwDataLen : 0x17 [Type: unsigned long]
[+0x010] pbDataBuff : 0x899af41c : 0x0 [Type: unsigned char *]
0: kd> db 0x899af3d8
899af3d8 94 f3 9a 89 68 f0 9a 89-24 f0 9a 89 00 00 00 00 ....h...$.......
899af3e8 5f 50 49 43 30 f3 9a 89-94 f3 9a 89 00 00 08 00 _PIC0...........
899af3f8 00 00 00 00 00 00 00 00-17 00 00 00 1c f4 9a 89 ................
899af408 00 00 00 00 00 00 00 00-48 4d 45 54 24 00 00 00 ........HMET$...
899af418 00 f0 9a 89 00 00 00 00-00 00 00 00 00 00 00 00 ................
899af428 00 00 00 00 01 70 68 47-50 49 43 00 48 4f 52 47 .....phGPIC.HORG
899af438 34 00 00 00 00 f0 9a 89-39 0e ab f7 84 00 00 00 4.......9.......
899af448 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................


0: kd> dt _methodobj 0x899af41c
ACPI!_MethodObj
+0x000 Mutex : _MutexObj
+0x010 bMethodFlags : 0x1 ''
+0x011 abCodeBuff : [1] "p"
0: kd> db 0x899af41c
899af41c 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
899af42c 01 70 68 47 50 49 4300-48 4f 52 47 34 00 00 00 .phGPIC.HORG4...


第二部分：
0: kd> t
eax=f742162e ebx=89dee000 ecx=00000001 edx=00000001 esi=89defed8 edi=00000001
eip=f742162e esp=f789a118 ebp=f789a130 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286
ACPI!Method:
f742162e 55 push ebp
0: kd> kc
#
00 ACPI!Method
01 ACPI!ParseTerm
02 ACPI!RunContext
03 ACPI!InsertReadyQueue
04 ACPI!RestartContext
05 ACPI!SyncLoadDDB
06 ACPI!AMLILoadDDB
07 ACPI!ACPIInitializeDDB
08 ACPI!ACPIInitializeDDBs
09 ACPI!ACPIInitialize
0a ACPI!ACPIInitStartACPI
0b ACPI!ACPIRootIrpStartDevice
0c ACPI!ACPIDispatchIrp
0d nt!IofCallDriver
0e nt!IopSynchronousCall
0f nt!IopStartDevice
10 nt!PipProcessStartPhase1
11 nt!PipProcessDevNodeTree
12 nt!PipDeviceActionWorker
13 nt!PipRequestDeviceAction
14 nt!IopInitializeBootDrivers
15 nt!IoInitSystem
16 nt!Phase1Initialization
17 nt!PspSystemThreadStartup
18 nt!KiThreadStartup

if ((rc = CreateNameSpaceObject(pctxt->pheapCurrent,
(PSZ)pterm->pdataArgs[0].pbDataBuff,
pctxt->pnsScope, pctxt->powner,
&pterm->pnsObj, 0)) == STATUS_SUCCESS)
{

0: kd> t
Breakpoint 47 hit
eax=89da334c ebx=89dee000 ecx=00000001 edx=00000001 esi=89defed8 edi=89defef8
eip=f741dc18 esp=f789a0e0 ebp=f789a114 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000202
ACPI!CreateNameSpaceObject:
f741dc18 55 push ebp
0: kd> dv
pheap = 0x89da3000
pszName = 0x89da3380 "\_PIC" 名字
pnsScope = 0x89da3024 目录路径
powner = 0x89da3330 所有者
ppns = 0x89defef8
dwfNS = 0
pns = 0x00000008
rc = 0n-146678760
pnsParent = 0x89da3380
iLen = 0n-1982189532

else
{
PMETHODOBJ pm = (PMETHODOBJ)pterm->pnsObj->ObjData.pbDataBuff;

#ifdef DEBUGGER
AddObjSymbol(pm->abCodeBuff, pterm->pnsObj);
#endif
MEMZERO(pterm->pnsObj->ObjData.pbDataBuff,
pterm->pnsObj->ObjData.dwDataLen);
pm->bMethodFlags = *(pctxt->pbOp - 1);
MEMCPY(&pm->abCodeBuff, pctxt->pbOp, pterm->pbOpEnd - pctxt->pbOp);
pctxt->pbOp = pterm->pbOpEnd;
}


第三部分：

NTSTATUS LOCAL Method(PCTXT pctxt, PTERM pterm)
{
TRACENAME("METHOD")
NTSTATUS rc = STATUS_SUCCESS;

ENTER(2, ("Method(pctxt=%x,pbOp=%x,pterm=%x)\n",
pctxt, pctxt->pbOp, pterm));

if ((rc = CreateNameSpaceObject(pctxt->pheapCurrent,
(PSZ)pterm->pdataArgs[0].pbDataBuff,
pctxt->pnsScope, pctxt->powner,
&pterm->pnsObj, 0)) == STATUS_SUCCESS)
{
pterm->pnsObj->ObjData.dwDataType = OBJTYPE_METHOD;
pterm->pnsObj->ObjData.dwDataLen = (ULONG)(FIELD_OFFSET(METHODOBJ,
abCodeBuff) +
pterm->pbOpEnd -
pctxt->pbOp);

if ((pterm->pnsObj->ObjData.pbDataBuff =
NEWMEOBJ(pctxt->pheapCurrent, pterm->pnsObj->ObjData.dwDataLen))
== NULL)
{
rc = AMLI_LOGERR(AMLIERR_OUT_OF_MEM,
("Method: failed to allocate method buffer"));
}
else
{
PMETHODOBJ pm = (PMETHODOBJ)pterm->pnsObj->ObjData.pbDataBuff;

#ifdef DEBUGGER
AddObjSymbol(pm->abCodeBuff, pterm->pnsObj);
#endif
MEMZERO(pterm->pnsObj->ObjData.pbDataBuff,
pterm->pnsObj->ObjData.dwDataLen);
pm->bMethodFlags = *(pctxt->pbOp - 1);
MEMCPY(&pm->abCodeBuff, pctxt->pbOp, pterm->pbOpEnd - pctxt->pbOp);
pctxt->pbOp = pterm->pbOpEnd;
}
}

EXIT(2, ("Method=%x (pnsObj=%x)\n", rc, pterm->pnsObj));
return rc;
} //Method

0: kd> dx -id 0,0,899a2278 -r1 ((ACPI!_List *)0x899af2d0)
((ACPI!_List *)0x899af2d0) : 0x899af2d0 [Type: _List *]
[+0x000] plistPrev : 0x899af268 [Type: _List *]
[+0x004] plistNext : 0x899af394 [Type: _List *]
0: kd> db 0x899af394
899af394 d0 f2 9a 89 d8 f3 9a 89-24 f0 9a 89 00 00 00 00 ........$.......
899af3a4 47 50 49 43 30 f3 9a 89-00 00 00 00 00 00 01 00 GPIC0...........
899af3b4 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
899af3c4 00 00 00 00 00 00 00 00-48 4e 53 4f 44 00 00 00 ........HNSOD...
899af3d4 00 f0 9a 89 94 f3 9a 89-68 f0 9a 89 24 f0 9a 89 ........h...$...
899af3e4 00 00 00 00 5f 50 49 43-30 f3 9a 89 94 f3 9a 89 ...._PIC0.......
899af3f4 00 00 08 00 00 00 00 00-00 00 00 00 17 00 00 00 ................
899af404 1c f4 9a 89 00 00 00 00-00 00 00 00 48 4d 45 54 ............HMET
0: kd> dt _nsobj 0x899af394
ACPI!_NSObj
+0x000 list : _List
+0x008 pnsParent : 0x899af024 _NSObj
+0x00c pnsFirstChild : (null)
+0x010 dwNameSeg : 0x43495047
+0x014 hOwner : 0x899af330 Void
+0x018 pnsOwnedNext : (null)
+0x01c ObjData : _ObjData
+0x030 Context : (null)
+0x034 dwRefCount : 0

版权声明: 本文来自互联网用户投稿，该文观点仅代表作者本人，不代表本站立场。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如若内容造成侵权/违法违规/事实不符，请联系邮箱：809451989@qq.com进行投诉反馈，一经查实，立即删除！
网站建设 2026/7/21 15:17:25

cocotb 配合 iverilog 搭建 Verilog 仿真工程

参考 cocotb文档 iverilog 配合 Makefile 搭建 Verilog 仿真工程 ModelSim 配合 Makefile 搭建 Verilog 仿真工程 目录结构 tree /f D:. ├─rtl │ adder.v │ └─sim│ Makefile│ test_adder.py文件 rtl/adder.v module adder (input wire clk…

作者头像 李华
网站建设 2026/7/21 22:46:04

GPU租赁服务推荐：专为HeyGem等AI应用优化配置

GPU租赁服务推荐：专为HeyGem等AI应用优化配置 在短视频内容爆炸式增长的今天，企业对高效、低成本的视频生产工具需求日益迫切。无论是品牌宣传、在线课程，还是虚拟客服与数字人直播，自动化生成“口型同步”的虚拟人视频已成为提升…

作者头像 李华
网站建设 2026/7/21 14:52:06

HeyGem系统运行实时日志路径说明：/root/workspace/运行实时日志.log

HeyGem系统运行实时日志路径说明：/root/workspace/运行实时日志.log 在AI数字人技术从实验室走向规模化落地的今天，系统的稳定性与可维护性正变得和模型精度一样重要。HeyGem作为一款基于大模型驱动的口型同步视频生成工具，面对的是教育、客服…

作者头像 李华
网站建设 2026/7/21 22:37:57

Three.js三维引擎无关？HeyGem聚焦二维视频合成

HeyGem：当数字人不再需要Three.js 在AI内容生产如火如荼的今天，我们常常被“3D建模”“实时渲染”“骨骼绑定”这类术语包围。仿佛没有一个强大的图形引擎，就做不了像样的数字人。但现实是，大多数企业并不需要电影级特效——他们只…

作者头像 李华
网站建设 2026/7/21 12:18:41

学生党如何体验？申请免费Token试用HeyGem基础功能

学生党如何体验？申请免费Token试用HeyGem基础功能 在短视频与AI内容创作全面爆发的今天，越来越多的学生开始尝试用技术手段制作课程汇报、项目展示甚至自媒体内容。但真人出镜拍摄耗时费力，剪辑门槛也不低；而市面上一些数字人工具…

作者头像 李华
网站建设 2026/7/14 23:44:24

Token计费模式探讨：未来HeyGem或引入用量计量机制

Token计费模式探讨：HeyGem的用量计量演进之路 在AI生成内容（AIGC）工具加速普及的今天，一个看似不起眼但至关重要的问题正浮出水面：我们该如何为一次“说话的数字人”视频生成准确地定价？是按分钟计费&#…

作者头像 李华