3dbrew

SVC: Difference between revisions

← Older edit
Emufan4568 (talk | contribs)
Trusted
34 edits
m Correct svc name from switchbrew
 
(64 intermediate revisions by 6 users not shown)
Line 432: Line 432:
| style="background: green" | Yes
| style="background: green" | Yes
| style="background: green" | Yes
| style="background: green" | Yes
| Break(BreakReason)
| Break(BreakReason reason)
Break(BreakReason debugReason, const void* croInfo, u32 croInfoSize)
|
|
|-
|-
Line 509: 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 574: Line 575:
| RestartDma(Handle, void *, void  const*, unsigned int, signed char)
| RestartDma(Handle, void *, void  const*, unsigned int, signed char)
|
|
|-
| 0x59
| style="background: green" | Yes
| style="background: red" | No?
| style="background: red" | No
| 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 635: Line 648:
| style="background: red" | No
| style="background: red" | No
| style="background: red" | No
| style="background: red" | No
| Result SetDebugThreadContext(Handle debug, u32 threadId, ThreadContext* context, u32 controlFlags)
| Result SetDebugThreadContext(Handle debug, u32 threadId, const ThreadContext* context, u32 controlFlags)
|
|
|-
|-
Line 642: Line 655:
| style="background: red" | No
| style="background: red" | No
| style="background: red" | No
| style="background: red" | No
| Result QueryDebugProcessMemory(MemoryInfo* blockInfo, PageInfo* pageInfo, Handle process, u32 addr)
| Result QueryDebugProcessMemory(MemoryInfo* blockInfo, PageInfo* pageInfo, Handle debug, u32 addr)
|
|
|-
|-
Line 670: Line 683:
| style="background: red" | No
| style="background: red" | No
| style="background: red" | No
| style="background: red" | No
| [[Multi-threading#GetDebugThreadParam|GetDebugThreadParam]](s64* unused, u32* out, Handle kdebug, u32 threadId, DebugThreadParam param)
| [[Multi-threading#GetDebugThreadParam|GetDebugThreadParam]](s64* unused, u32* out, Handle kdebug, u32 threadId, DebugThreadParameter param)
| Disabled on regular kernel.
|  
|- style="border-top: double"
|- style="border-top: double"
| 0x70
| 0x70
Line 684: 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 691: 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 740: Line 753:
| style="background: red" | No
| style="background: red" | No
| style="background: red" | No
| style="background: red" | No
| Result SetResourceLimitValues(Handle res_limit, LimitableResource* resource_type_list, s64* resource_list, u32 count)
| Result SetResourceLimitLimitValues(Handle res_limit, LimitableResource* resource_type_list, s64* resource_list, u32 count)
|
|
|-
|-
Line 777: Line 790:
| style="background: green" | Yes
| style="background: green" | Yes
| style="background: green" | Yes
| style="background: green" | Yes
| Result SignalBreakpointDebugEvent(void)
| Stop point
| The svcaccesscontrol mask doesn't apply for this SVC. This svc doesn't check the "debug mode enabled" flag either. Does nothing if there is no [[KDebug]] object associated to the current process. Stubbed on ARM9 NATIVE_FIRM.
| The svcaccesscontrol mask doesn't apply for this SVC. This svc doesn't check the "debug mode enabled" flag either. Does nothing if there is no [[KDebug]] object associated to the current process. Stubbed on ARM9 NATIVE_FIRM.
|}
|}
Line 844: Line 857:


== struct DebugEventInfo ==
== struct DebugEventInfo ==
Size: 0x28 bytes
When using svcGetProcessDebugEvent, the kernel fetches the first [[KEventInfo]] instance of the process's [[KDebug]]. The debug event is handled and parsed into this structure.


{| class="wikitable" border="1"
{| class="wikitable" border="1"
Line 855: Line 871:
| Thread ID (not used in all events)
| Thread ID (not used in all events)
|-
|-
| u32[2]
| u32
| Unknown/padding
| Flags. Bit0 means that svcContinueDebugEvent needs to be called for this event
|-
| u8[4]
| Remnants of the corresponding flags in [[KEventInfo]], always 0 here
|-
|-
| u32[6]
| u32[6]
Line 866: Line 885:
!  Id
!  Id
|-
|-
| PROCESS
| ATTACH PROCESS
| 0
| 0
|-
|-
| CREATE THREAD
| ATTACH THREAD
| 1
| 1
|-
|-
Line 875: Line 894:
| 2
| 2
|-
|-
| EXIT PROCESS
| EXIT PROCESS (1)
| 3
| 3
|-
|-
Line 881: 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 902: Line 921:
| 11
| 11
|-
|-
| MAP
| MAP (1) (2)
| 12
| 12
|}
|}


=== PROCESS event ===
<nowiki>(1)</nowiki> Non-blocking: all other events preempt and block all the threads of their process until they are continued.
 
<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.
 
ATTACH THREAD events are also emitted when a thread is created from an attached process.
 
=== ATTACH PROCESS event ===


{| class="wikitable" border="1"
{| class="wikitable" border="1"
Line 922: Line 951:
|-
|-
| u32
| u32
| 0 = newly created process, 1 = attached process
| "Other" flag. Always 0 in available kernel versions
|}
|}


=== CREATE THREAD event ===
=== ATTACH THREAD event ===


{| class="wikitable" border="1"
{| class="wikitable" border="1"
Line 932: Line 961:
|-
|-
| u32
| u32
| Creator thread ID
| Creator thread ID (0 if attached by svcDebugActiveProcess)
|-
|-
| u32
| void *
| Base address (?)
| Thread local storage
|-
|-
| u32
| u32 *
| Entrypoint
| Entrypoint = .text load address of the parent process
|}
|}


Line 974: Line 1,003:
| 1
| 1
|-
|-
| UNHANDLED EXCEPTION
| DEBUG TERMINATE
| 2
| 2
|}
|}
Line 990: Line 1,019:
| Exception address
| Exception address
|-
|-
| u32
| u32[4]
| Argument (type-specific)
| Type-specific data, see below
|}
|}


Exception types:
Exception types:
{| class="wikitable" border="1"
{| class="wikitable" border="1"
!  Reason
!  Exception type
!  Id
!  Id
!  Argument
|-
|-
| UNDEFINED INSTRUCTION
| UNDEFINED INSTRUCTION
| 0
| 0
| register storage
|-
|-
| PREFETCH ABORT
| PREFETCH ABORT
| 1
| 1
| register storage
|-
|-
| DATA ABORT
| DATA ABORT
| 2
| 2
| register storage
|-
|-
| VFP EXCEPTION
| UNALIGNED DATA ACCESS
| 3
| 3
| [[ERR:Throw#ExceptionInfo|ExceptionInfo]]
|-
|-
| ATTACH BREAK
| ATTACH BREAK
| 4
| 4
| (None)
|-
|-
| BREAKPOINT
| STOP POINT
| 5
| 5
| (None)
|-
|-
| USER BREAK
| USER BREAK
| 6
| 6
| User break type
|-
|-
| DEBUGGER BREAK
| DEBUGGER BREAK
| 7
| 7
| (None)
|-
|-
| UNDEFINED SYSCALL
| UNDEFINED SYSCALL
| 8
| 8
| Attempted syscall ID
|}
|}


The register storage layout is as follows (referring to user-mode registers): r0-r12, sp, <event-signaling exception handler>, lr_svc, lr, pc (misadjusted for Thumb instructions), cpsr.
==== UNDEFINED INSTRUCTION/PREFETCH ABORT/DATA ABORT/UNALIGNED DATA ACCESS/UNDEFINED SYSCALL events ====
{| class="wikitable" border="1"
!  Type
!  Field
|-
| u32
| Fault information: Fault Address Register (for DATA ABORT and UNALIGNED DATA ACCESS),
attempted SVC ID (for UNDEFINED SYSCALL), otherwise 0
|}
 
==== STOP POINT event ====
{| class="wikitable" border="1"
!  Type
!  Field
|-
| u32
| Stop point type that caused the event: 0 = svc 0xFF, 1 = breakpoint, 2 = watchpoint
|-
| u32
| Fault information: FAR for watchpoints, 0 otherwise
|}
 
==== USER BREAK event ====
{| class="wikitable" border="1"
!  Type
!  Field
|-
| u32
| Break reason
|-
| u32[2]
| Info for LOAD_RO and UNLOAD_RO
|}


User break types:
User break types:
Line 1,052: Line 1,103:
| USER
| USER
| 2
| 2
|-
| LOAD_RO
| 3
|-
| UNLOAD_RO
| 4
|}
|}


=== SCHEDULER/SYSCALL IN/OUT events ===
==== DEBUGGER BREAK event ====
{| class="wikitable" border="1"
!  Type
!  Field
|-
| s32[4]
| 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).
|}
 
=== SCHEDULE/SYSCALL IN/OUT events ===


{| class="wikitable" border="1"
{| class="wikitable" border="1"
Line 1,064: Line 1,130:
|-
|-
| u32
| u32
| Syscall (only for SYSCALL events)
| CPU ID (SCHEDULE events) Syscall (SYSCALL events)
|}
|}


Line 1,099: Line 1,165:
|}
|}


== enum DebugThreadParam ==
== struct ThreadContext ==
 
Size: 0xCC bytes
 
{| class="wikitable" border="1"
|-
!  Offset
! Type
!  Description
|-
| 0x0
| CpuRegisters
| Saved CPU registers (r0-r12, sp, lr, pc, cpsr)
|-
| 0x44
| FpuRegisters
| Saved FPU registers (d0-d15, fpscr, fpexc)
|}
 
The user needs to adjust pc for exceptions that occured while in Thumb mode.
 
'''Flags for svcGetDebugThreadContext/svcSetDebugThreadContext''':
 
{| class="wikitable" border="1"
|-
! Bit
! Description
|-
| 0
| Get/set CPU GPRs (r0-r12)
|-
| 1
| Get/set CPU SPRs (sp, lr, pc, cpsr)
|-
| 2
| Get/set FPU GPRs (d0-d15 aka. f0-f31)
|-
| 3
| Get/set FPU SPRs (fpscr, fpexc)
|}
 
When setting CPSR, the following assignment is done: <code>ctx->cpsr = ctx->cpsr & 0x7F0FDFF | userCtx->cpuRegisters.cpsr & 0xF80F0200;</code>. This is to avoid obvious security issues.
 
== enum DebugThreadParameter ==


{| class="wikitable" border="1"
{| class="wikitable" border="1"
Line 1,108: Line 1,217:
| 0
| 0
|-
|-
| SCHEDULE
| SCHEDULING_MASK_LOW
| 1
| 1
|-
|-
Line 1,174: 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,202: 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, if and only if both UNITINFO and [[Configuration_Memory#0x1FF80015|0x1FF80015]] are not 0, 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
| Yes
| Yes
| No
| No
| Arguments: <code>u64 unk</code>
| Arguments: <code>u32 what, u64 val</code>
What this does depends of the value of the field that was stored in [[Configuration_Memory|0x1FF80015]].  
UNITINFO needs to be non-zero for <code>what</code> 1 and 2.  


If this is 0 (Prod) or any invalid value, nothing is done. If it is 1 (Dev), <code>unk != 0</code> is written to some global variable; if this variable has bit0 clear, the regdump will be written when an exception occurs in a privileged mode (the destination depends on fields in the local storage of the current thread at the time of the exception).  
If <code>what</code> is 0 or any invalid value, nothing is done.  


If 2 (Debugger), it's written to the following byte.  
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 3 (Firm), this calls a scheduler-related function with <code>(u32)unk</code> which performs a context switch, and that value to a global variable if its contents are not equal to the arg, under certain conditions (returns error 0xC8A01414 otherwise).
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.
|-
|-
| 7
| 7
Line 1,229: 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
| Yes, implemented at some point after system-version v4.5.
| Yes, implemented at some point after system-version v4.5.
| ?
| ?
| Argumens: <code>u64 unk</code>.
| Argumens: <code>u64 titleID</code>.
Writes <code>unk</code> to some global variable, but the latter doesn't seem to be used anywhere else.
When creating a process, if the process has a non-zero TID equal to the parameter above (which is stored in a global variable), then KProcessHwInfo+0x32 ("process is the currently running app") is set to <code>true</code>.
Used by NS conditionally based on the contents of the [[NS CFA]].
|-
|-
| 10
| 10
Line 1,295: Line 1,405:
!  Description
!  Description
|-
|-
| 9-19
| 0
|
| 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
|
| Returns the amount of <related unused field> + total supervisor-mode stack size + page-rounded size of the external handle table
|-
| 2
|
| 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
|
| Returns the amount of <related unused field> + total supervisor-mode stack size + page-rounded size of the external handle table
|-
| 4
|
| Returns the amount of handles in use by the process.
|-
| 5
|
| Returns the highest count of handles that have been open at once by the process
|-
| 6
|
| Returns <code>*(u32*)(KProcess+0x234)</code> which is always 0
|-
| 7
|
| Returns the number of threads of the process
|-
| 8
|
| Returns the maximum number of threads which can be opened by this process (always 0)
|-
| 9-18
| [[8.0.0-18]]
| [[8.0.0-18]]
| This only returns error 0xD8E007ED.
| This only returns error 0xD8E007ED.
|-
| 19
| 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 (memory region flag). High out u32 = 0.
|-
|-
| 20
| 20
Line 1,303: Line 1,453:
| low u32 = (0x20000000 - <LINEAR virtual-memory base for this process>). That is, the output value is the value which can be added to LINEAR memory vaddrs for converting to physical-memory addrs.
| low u32 = (0x20000000 - <LINEAR virtual-memory base for this process>). That is, the output value is the value which can be added to LINEAR memory vaddrs for converting to physical-memory addrs.
|-
|-
| 21-23
| 21
| [[8.0.0-18]]
| [[8.0.0-18]]. N3DS only.
| This only returns 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
| [[8.0.0-18]]. N3DS only.
| Returns the base VA of the QTM static mem block reserved in the exheader, otherwise 0 (+ error 0xE0E01BF4) if it doesn't exist
|-
| 23
| [[8.0.0-18]]. N3DS only.
| Returns the size of the QTM static mem block reserved in the exheader, otherwise 0 (+ error 0xE0E01BF4) if it doesn't exist
|}
|}


Line 1,318: 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,326: Line 1,487:
= svc7B Backdoor =
= svc7B Backdoor =
This saves SVC-mode SP+LR on the user-mode stack, then sets the SVC-mode SP to the user-mode SP. This then calls the specified code in SVC-mode. Once the called code returns, this pops the saved SP+LR off the stack for restoring the SVC-mode SP, then returns from the svc7b handler. Note that this svc7b handler does not disable IRQs, if any IRQs/context-switches occur while the SVC-mode SP is set to the user-mode one here, the ARM11-kernel will crash(which hangs the whole ARM11-side system).
This saves SVC-mode SP+LR on the user-mode stack, then sets the SVC-mode SP to the user-mode SP. This then calls the specified code in SVC-mode. Once the called code returns, this pops the saved SP+LR off the stack for restoring the SVC-mode SP, then returns from the svc7b handler. Note that this svc7b handler does not disable IRQs, if any IRQs/context-switches occur while the SVC-mode SP is set to the user-mode one here, the ARM11-kernel will crash(which hangs the whole ARM11-side system).
= svc 0x59 =
Implemented with [[11.3.0-36|11.3.0-X]]. Used with GSP module starting with that version. This always returns 0.
When input_flag is not 0x1, it will use value 0x0 internally. When a state field already matches input_flag, this will immediately return. Otherwise, after this SVC finishes running, it will write input_flag to this state field. GSP module uses 0x0 for APPLICATION-memregionid and 0x1 for non-APPLICATION-memregionid.
This writes "<nowiki>0x100 | <val></nowiki>" to [[CONFIG11_Registers#CFG11_GPUPROT|pdnregbase+0x140]], where val depends on input_flag and a kernel state field for [[Configuration_Memory|APPMEMTYPE]].
When input_flag is 0x1 val is fixed:
* Old3DS: 0x3
* New3DS: 0x460
Otherwise, val depends on the kernel APPMEMTYPE state field:
{| class="wikitable" border="1"
|-
!  FIRM
!  [[Memory_layout|APPMEMTYPE]]
!  val
|-
| Old3DS
| 2
| 0x3
|-
| Old3DS
| 3
| 0x5
|-
| Old3DS
| 4
| 0x6
|-
| Old3DS
| Non-value-{2/3/4}
| 0x7
|-
| New3DS
| 7
| 0x490
|-
| New3DS
| Non-value-7
| 0x4F0
|}
This same register is also initialized during kernel boot starting with [[3.0.0-5]], with the following values:
* Old3DS: 0x103
* 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 =
Retrieved from "https://www.3dbrew.org/wiki/SVC"