summaryrefslogtreecommitdiff
path: root/nids/360
diff options
context:
space:
mode:
authorDavee2018-10-28 16:33:11 +0000
committerDavee2018-10-28 16:39:30 +0000
commita1c5ac3005c9d083b00826b7e8129fcd98e862d8 (patch)
tree93e4c69c36a726597aae6d7c8666f5ba873166b4 /nids/360
parentcorrect spelling error in documentation (diff)
downloadvds-libraries-a1c5ac3005c9d083b00826b7e8129fcd98e862d8.tar.gz
add ksceKernelGetThreadCpuRegisters
This function is used to get the state of the registers for a SUSPENDED thread. It returns the registers in a two part structure. It's uncertian what the difference is between the two parts. It seems like its a user/kernel separation, but it's uncertain. It could also be a current/exception difference, but it is unconvincing. In normal usage on a suspended thread it seems to be the user aspect that contains valid values. When you query a suspended thread that has no had the opportunity to start yet, the kernel side is filled.
Diffstat (limited to 'nids/360')
-rw-r--r--nids/360/SceKernelThreadMgr.yml1
1 files changed, 1 insertions, 0 deletions
diff --git a/nids/360/SceKernelThreadMgr.yml b/nids/360/SceKernelThreadMgr.yml
index 75972f6..fb25df9 100644
--- a/nids/360/SceKernelThreadMgr.yml
+++ b/nids/360/SceKernelThreadMgr.yml
@@ -137,6 +137,7 @@ modules:
sceKernelGetSystemTimeLow: 0x47F6DE49
sceKernelGetSystemTimeWide: 0xF4EE4FA9
sceKernelGetThreadCpuAffinityMask: 0x83DC703D
+ sceKernelGetThreadCpuRegisters: 0x5022689D
sceKernelGetThreadCurrentPriority: 0x01414F0B
sceKernelGetThreadId: 0x59D06540
sceKernelGetThreadIdList: 0xEA7B8AEF