From a1c5ac3005c9d083b00826b7e8129fcd98e862d8 Mon Sep 17 00:00:00 2001
From: Davee
Date: Sun, 28 Oct 2018 16:33:11 +0000
Subject: 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.
---
 nids/360/SceKernelThreadMgr.yml | 1 +
 1 file changed, 1 insertion(+)

(limited to 'nids/360')

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
-- 
cgit v1.2.3