Changes

Jump to navigation Jump to search
613 bytes added ,  23:20, 30 May 2020
Lots of misinfo in there →‎GetProcessInfo
Line 510: Line 510:  
| style="background: red" | No
 
| style="background: red" | No
 
| style="background: red" | No
 
| style="background: red" | No
| Result [[IPC|ReplyAndReceive]](s32* index, Handle* handles, s32 handleCount, Handle replyTarget)
+
| Result [[IPC#svcReplyAndReceive|ReplyAndReceive]](s32* index, Handle* handles, s32 handleCount, Handle replyTarget)
 
|
 
|
 
|-
 
|-
Line 580: Line 580:  
| style="background: red" | No?
 
| style="background: red" | No?
 
| style="background: red" | No
 
| style="background: red" | No
| Implemented with [[11.3.0-36|11.3.0-X]], see below. (s8 input_flag)
+
| SetGpuProt(s8 input_flag). Implemented with [[11.3.0-36|11.3.0-X]], see below.
 +
|-
 +
| 0x5A
 +
| style="background: green" | Yes
 +
| style="background: red" | No?
 +
| style="background: red" | No
 +
| SetWifiEnabled(s0 input_flag). Implemented with [[11.4.0-37|11.4.0-X]], see below.
 
|- style="border-top: double"
 
|- style="border-top: double"
 
| 0x60  
 
| 0x60  
Line 691: Line 697:  
| style="background: red" | No
 
| style="background: red" | No
 
| style="background: red" | No
 
| style="background: red" | No
| Result [[Memory Management#Memory_Mapping|MapProcessMemory]](Handle KProcess, unsigned int StartAddr, unsigned int EndAddr)
+
| Result [[Memory Management#Memory_Mapping|MapProcessMemory]](Handle process, u32 startAddr, u32 size)
 
|
 
|
 
|-
 
|-
Line 698: Line 704:  
| style="background: red" | No
 
| style="background: red" | No
 
| style="background: red" | No
 
| style="background: red" | No
| Result [[Memory Management#Memory_Mapping|UnmapProcessMemory]](Handle KProcess, unsigned int StartAddr, unsigned int EndAddr)
+
| Result [[Memory Management#Memory_Mapping|UnmapProcessMemory]](Handle process, u32 startAddr, u32 size)
 
|
 
|
 
|-
 
|-
Line 866: Line 872:  
|-
 
|-
 
| u32
 
| u32
| Flags. Bit0 means that svcContinueDebugEvent needs to be called for this event (except for EXIT PROCESS events, for which you need to call svcContinueDebugEvent even if this bit is clear)
+
| Flags. Bit0 means that svcContinueDebugEvent needs to be called for this event
 
|-
 
|-
 
| u8[4]
 
| u8[4]
Line 888: Line 894:  
| 2
 
| 2
 
|-
 
|-
| EXIT PROCESS
+
| EXIT PROCESS (1)
 
| 3
 
| 3
 
|-
 
|-
Line 894: Line 900:  
| 4
 
| 4
 
|-
 
|-
| DLL LOAD *
+
| DLL LOAD (3)
 
| 5
 
| 5
 
|-
 
|-
| DLL UNLOAD *
+
| DLL UNLOAD (3)
 
| 6
 
| 6
 
|-
 
|-
| SCHEDULE IN **
+
| SCHEDULE IN (1) (2)
 
| 7
 
| 7
 
|-
 
|-
| SCHEDULE OUT *
+
| SCHEDULE OUT (1) (2)
 
| 8
 
| 8
 
|-
 
|-
| SYSCALL IN *
+
| SYSCALL IN (1) (2)
 
| 9
 
| 9
 
|-
 
|-
| SYSCALL OUT *
+
| SYSCALL OUT (1) (2)
 
| 10
 
| 10
 
|-
 
|-
Line 915: Line 921:  
| 11
 
| 11
 
|-
 
|-
| MAP *
+
| MAP (1) (2)
 
| 12
 
| 12
 
|}
 
|}
   −
<nowiki>*</nowiki> Unused
+
<nowiki>(1)</nowiki> Non-blocking: all other events preempt and block all the threads of their process until they are continued.
   −
<nowiki>**</nowiki> Referenced but never used in practise
+
<nowiki>(2)</nowiki> There is handling code in the kernel but nothing signal those events.
 +
 
 +
<nowiki>(3)</nowiki> Completely removed from the kernel, but referenced in DMNT. Stubbed relocation code (e.g., in Process9 and in PXI sysmodule) and even whole libraries (e.g., in PXI sysmodule's .rodata section) seem to indicate that Nintendo used dynamic libraries early in system development.
    
When calling svcDebugActiveProcess, an ATTACH PROCESS debug event is signaled, then ATTACH THREAD for each of its opened threads, then finally ATTACH BREAK.
 
When calling svcDebugActiveProcess, an ATTACH PROCESS debug event is signaled, then ATTACH THREAD for each of its opened threads, then finally ATTACH BREAK.
Line 995: Line 1,003:  
| 1
 
| 1
 
|-
 
|-
| UNHANDLED EXCEPTION
+
| DEBUG TERMINATE
 
| 2
 
| 2
 
|}
 
|}
Line 1,108: Line 1,116:  
!  Field
 
!  Field
 
|-
 
|-
| [[KThread]]*[4]
+
| s32[4]
| Pointers to the attached process's that were running, on each core, at the time svcBreakDebugProcess was called
+
| IDs of the attached process's threads that were running on each core at the time of the @ref svcBreakDebugProcess call, or -1 (only the first 2 values are meaningful on O3DS).
Only the first two entries are relevant on O3DS.
   
|}
 
|}
   Line 1,276: Line 1,283:  
| Yes
 
| Yes
 
| No
 
| No
| Arguments : <code>u64 firmTitleID</code> (O3DS) or <code>u64 firmTitleID, u32 unknown</code> (N3DS, pm-module uses value 0 with this)
+
| Arguments : <code>u64 firmTitleID</code> (the high 32-bits of that title ID (0 when using N3DS pm) have a special meaning on N3DS, they're otherwise ignored, see below).
This initializes the programID for launching [[FIRM]], then triggers launching [[FIRM]]. With New3DS kernel, it forces the programIDlow to be the New3DS NATIVE_FIRM, when the input programIDlow is for the Old3DS NATIVE_FIRM and Param2==0. On New3DS, the kernel disables the additional New3DS cache hw prior to calling the firmlaunch function from the <handler for the KernelSetState-types called via funcptr>.
+
This initializes the programID for launching [[FIRM]], then triggers launching [[FIRM]]. With New3DS kernel, it forces the firm title ID to be the New3DS NATIVE_FIRM, when the input firm title ID is 2. The high firm title ID is always set to 0x40138. On New3DS, the kernel disables the additional New3DS cache hw prior to calling the firmlaunch function from the <handler for the KernelSetState-types called via funcptr>.
 
|-
 
|-
 
| 1
 
| 1
Line 1,304: Line 1,311:  
| Yes
 
| Yes
 
| Yes
 
| Yes
| Used by kernelpanic. This makes core0 enter a WFI/B infinite loop. Threads that were created on core1 or core2 have their priority set to 0x3F, except if the thread was created on core1 and whose parent process (if any) has the "Runnable on sleep" [[NCCH/Extended_Header#ARM11_Kernel_Flags|ARM11 kernel flag]] set. Core1 threads with a priority of 0x40 without a parent process have their priority set to 0x3E.
+
| Power state change. Takes one u32 parameter.
   −
Prior to first invoking this handler, the global variable holding <code>UNITINFO != 0</code> is true, and if there is no [[LCD_Registers#Fill_Color|LCD fill]] set at the time kernelpanic is called, kernelpanic fill the top screen with white (it does the same for the bottom screen if the current process is running under the APPLICATION memregion).
+
0: shutdown/reboot. hangs the Arm11. Used by kernelpanic and PTM. This makes all cores enter a WFI/B infinite loop.  
 
  −
Before invoking this handler a second time, kernelpanic wait for the user to hold L+R+Start+Select down.
   
|-
 
|-
 
| 6
 
| 6
Line 1,314: Line 1,319:  
| No
 
| No
 
| Arguments: <code>u32 what, u64 val</code>
 
| Arguments: <code>u32 what, u64 val</code>
UNITINFO needs to be non-zero.  
+
UNITINFO needs to be non-zero for <code>what</code> 1 and 2.  
    
If <code>what</code> is 0 or any invalid value, nothing is done.  
 
If <code>what</code> is 0 or any invalid value, nothing is done.  
   −
If it is 1, <code>val != 0</code> is written to the global variable enabling ERR:F-format register dumps on user-mode CPU/VFP exceptions (the VFP exception handler acts as if this variable was always true and works on retail environments). The user handler, stack pointer to use for exception handling, and pointer to use for the exception info structure are contiguously located in either the thread's TLS, or if the handler is NULL, in the main thread's TLS, at offset 0x40. If the specified stack pointer is 1, sp_usr - 0x5c is used instead; if the specified exception info buffer is 1, sp_usr - 0x5c is used instead, and if it is 0, <specified stack> - 0x5c is used (0x5c is the size of the exception info structure that is being pushed). Configured by NS on startup on dev-units (default being 0 on non-debugger/jtag units).
+
If it is 1, <code>val != 0</code> is written to the global variable enabling ERR:F-format register dumps on user-mode CPU/VFP exceptions (the VFP exception handler acts as if this variable was always true and works on retail environments). The user handler, stack pointer to use for exception handling, and pointer to use for the exception info structure are contiguously located in either the thread's TLS, or if the handler is NULL, in the main thread's TLS, at offset 0x40. If the specified stack pointer is 1, sp_usr - 0x5c is used instead; if the specified exception info buffer is 1, sp_usr - 0x5c is used instead, and if it is 0, <specified stack> - 0x5c is used (0x5c is the size of the exception info structure that is being pushed). Configured by NS on startup on dev-units (default being 0 on non-debugger/jtag units) using the 0x000F0000 configuration block in the [[Config_Savegame|config savegame]].
   −
If 2, kernelpanic will be called when svcBreak is used by a non-attached process. Configured by NS on startup on dev-units (default being 0 on non-debugger/jtag units).
+
If 2, kernelpanic will be called when svcBreak is used by a non-attached process. Configured by NS on startup on dev-units (default being 0 on non-debugger/jtag units) using the 0x000F0000 configuration block in the [[Config_Savegame|config savegame]].
    
If 3, this changes the scheduling/preemption mode (when no threads are being preempted, otherwise returns error 0xC8A01414), see [[KResourceLimit]] for more details.
 
If 3, this changes the scheduling/preemption mode (when no threads are being preempted, otherwise returns error 0xC8A01414), see [[KResourceLimit]] for more details.
Line 1,333: Line 1,338:  
| Yes
 
| Yes
 
| No
 
| No
| Alternate FIRM launch code-path, with different [[PXI]] FIFO word constants. Usually not used. PTM-sysmodule can use this but it's unknown what exactly triggers that in PTM-sysmodule.
+
| Hangs the Arm9, using a code path similar to the one used on firmlaunch. Used by PTM on shutdown/reboot.
 
|-
 
|-
 
| 9
 
| 9
Line 1,402: Line 1,407:  
| 0
 
| 0
 
|  
 
|  
| Returns the amount of executable memory allocated to the process + thread context size + page-rounded size of the external handle table
+
| Returns the amount of private (code, data, regular heap) and shared memory used by the process + total supervisor-mode stack size + page-rounded size of the external handle table. This is the amount of physical memory the process is using, minus TLS, main thread stack and linear memory.
 
|-
 
|-
 
| 1
 
| 1
 
|  
 
|  
| Returns the amount of <unknown> memory allocated to the process + thread context size + page-rounded size of the external handle table
+
| Returns the amount of <related unused field> + total supervisor-mode stack size + page-rounded size of the external handle table
 
|-
 
|-
 
| 2
 
| 2
 
|  
 
|  
| Returns the amount of DMA-able (code, data, IO pages, etc.) memory allocated to the process + thread context size + page-rounded size of the external handle table
+
| Returns the amount of private (code, data, heap) memory used by the process + total supervisor-mode stack size + page-rounded size of the external handle table
 
|-
 
|-
 
| 3
 
| 3
 
|  
 
|  
| Returns the amount of <unknown> memory allocated to the process + thread context size + page-rounded size of the external handle table
+
| Returns the amount of <related unused field> + total supervisor-mode stack size + page-rounded size of the external handle table
 
|-
 
|-
 
| 4
 
| 4
 
|  
 
|  
| Returns the amount handles in use by the process.
+
| Returns the amount of handles in use by the process.
 
|-
 
|-
 
| 5
 
| 5
Line 1,430: Line 1,435:  
| 7
 
| 7
 
|  
 
|  
| Returns 0
+
| Returns the number of threads of the process
 
|-
 
|-
 
| 8
 
| 8
Line 1,442: Line 1,447:  
| 19
 
| 19
 
| Stub: [[8.0.0-18]]. Implementation: [[11.3.0-36|11.3.0-X]].
 
| Stub: [[8.0.0-18]]. Implementation: [[11.3.0-36|11.3.0-X]].
| Originally this only returned 0xD8E007ED. Now with v11.3 this returns the memregion for the process: out low u32 = [[KProcess]] "Kernel flags from the exheader kernel descriptors" & 0xF00. High out u32 = 0.
+
| Originally this only returned 0xD8E007ED. Now with v11.3 this returns the memregion for the process: out low u32 = [[KProcess]] "Kernel flags from the exheader kernel descriptors" & 0xF00 (memory region flag). High out u32 = 0.
 
|-
 
|-
 
| 20
 
| 20
Line 1,450: Line 1,455:  
| 21
 
| 21
 
| [[8.0.0-18]]. N3DS only.
 
| [[8.0.0-18]]. N3DS only.
| Returns the maximum amount of VRAM memory allocatable by the process: 0x800000 bytes if the process has already allocated VRAM memory, otherwise 0 (+ error 0xE0E01BF4)
+
| Returns the VA -> PA conversion offset for the QTM static mem block reserved in the exheader (0x800000), otherwise 0 (+ error 0xE0E01BF4) if it doesn't exist
 
|-
 
|-
 
| 22
 
| 22
 
| [[8.0.0-18]]. N3DS only.
 
| [[8.0.0-18]]. N3DS only.
| Returns the address of the first chunk of VRAM allocated by this process
+
| Returns the base VA of the QTM static mem block reserved in the exheader, otherwise 0 (+ error 0xE0E01BF4) if it doesn't exist
 
|-
 
|-
 
| 23
 
| 23
 
| [[8.0.0-18]]. N3DS only.
 
| [[8.0.0-18]]. N3DS only.
| Returns the amount of VRAM allocated by this process (?)
+
| Returns the size of the QTM static mem block reserved in the exheader, otherwise 0 (+ error 0xE0E01BF4) if it doesn't exist
 
|}
 
|}
   Line 1,471: Line 1,476:  
|-
 
|-
 
| 1
 
| 1
| Get internal refcount-1 for kernel object (u32), and also a boolean if the refcount-1 is negative (u32).
+
| Get internal refcount for kernel object (not counting the one this SVC adds internally to operate), sign-extended to 64 bits.
 +
|-
 +
| 2
 +
| Unimplemented, returns an uninitialized u64 variable (corresponding to r5-r6, which were not altered outside of userland).
 
|-
 
|-
 
| 0x32107
 
| 0x32107
Line 1,526: Line 1,534:  
* Old3DS: 0x103
 
* Old3DS: 0x103
 
* New3DS: 0x550
 
* New3DS: 0x550
 +
 +
= svc 0x5A =
 +
Like what NWM did previously, this one does the following:
 +
 +
  if (in_flag)
 +
    CFG11_WIFICNT |= 1;
 +
  else
 +
    CFG11_WIFICNT &= ~1;
    
= Kernel error-codes =
 
= Kernel error-codes =
516

edits

Navigation menu