96 KiB
96 KiB
libkernel technical debt
Build
- winpthreads initializes a statically initialized rwlock on its first lock and fails a concurrent first lock with
EINVAL, whichstd::shared_mutexandstd::shared_timed_mutexignore, so that lock does not exclude. Guest rwlocks (Pthread.hpp) and the hoststd::shared_mutexobjects in Recompiler.cpp are locked once when created. A new hoststd::shared_mutexused on Windows needs the same.
Silent stubs
- scePthreadMutexattrSetprotocol (libkernel) - accepts 0 to 2 as a PS5 (firmware 13.60) does and returns
EINVALotherwise, but the protocol is not stored or applied: priority inheritance and protection are not modelled. On the console a null or uninitialized mutex attribute returnsEINVALfrom the SCE attribute calls,scePthreadMutexInittakes an uninitialized attribute as the default one, and a destroyed mutex returnsEINVALfromscePthreadMutexDestroy; a null mutex pointer crashed the payload and still throws - pthread_mutexattr_setprotocol, pthread_mutexattr_setprioceiling, pthread_mutexattr_getprioceiling (libkernel) - the protocol and the priority ceiling are stored and reported as in FreeBSD's libthr (the ceiling is set or read only under
PTHREAD_PRIO_PROTECT, and setting a protocol resets it to the highestSCHED_RRpriority), but mutexes do not apply them: a priority-inherit or priority-protect mutex locks like a normal one and does not change its owner's priority - sceKernelGetMainSocId and sceKernelGetCpumode (libkernel) both return 0, and sceKernelGetCpuFrequency returns the host TSC frequency measured for
sceKernelGetTscFrequency, not the console CPU clock. The PS5's SoC id and CPU mode are unknown; shadPS4's PS4 values are 0x710f10/0x740f30 and 0, 2 or 5 from the param.sfo CPU-mode flags. PPSA99203 only logs them ([console] main SoC id: result=%#x out=%#x,CPU: %llu Hz, cpumode %d), passing a pointer thatsceKernelGetMainSocIdleaves untouched - sceKernelEnableDmemAliasing (libkernel) returns 0 and changes nothing: direct memory can always be mapped more than once here, as
DoMapDirectin DirectMemory.cpp only checks that the physical pages are allocated, so there is no aliasing to turn on. shadPS4 (PS4) sets a flag there that lifts theEBUSYitssceKernelMapDirectMemory2, andsceKernelMapDirectMemoryfor SDK 2.50 and later, return for direct memory that is already mapped; that check is not applied here. The no-argumentintsignature follows shadPS4 and ProsperoEden (PPSA99008), which calls it before mapping the same direct memory again. Whether the PS5 refuses such a mapping without the call is unverified - sceKernelInternalMemoryGetAvailableSize (libkernel) reports 0 bytes and returns 0: what the console's internal memory pool holds and how large it is are unknown. The
int (size_t*)signature is from xUtilty (PS4). PPSA99203 calls it once besidesceKernelAvailableFlexibleMemorySizewhile starting its GS renderer and never reads the result (GS.cpp)
Unknown function info
- getlogin_r (libkernel) returns the host effective account name:
GetUserNameWas UTF-8 on Windows andgetpwuid_r(geteuid())on POSIX. A valid account returns a name even without a login session; hostgetlogin_r,USERandLOGNAMEare not consulted. The console's login name and behaviour without a session are unknown. Account lookup or encoding failures, a missing or empty account name, and POSIX account records exceeding the 16 KiB lookup buffer throw; there is no replacement name or retry. A short guest buffer returnsERANGEwithout modifying it, and a null output returnsEFAULT. - sceCoredumpGetThreadContextInfo (libkernel, NID
ShChva57wIM) - declared as a throwing stub. The pointer and size arguments and integer return type follow SharpProspero's PS5 bindings. The context structure and console behavior are unverified; the stub does not read or write caller memory. PPSA01736 imports it - sceKernelGetSystemSwVersion (libkernel) reports baseline system software version
0x01000000("01.000.000") for ProsperoStore (PPSA99000). The 0x28-byte layout (uint64_t sizeat 0,versionStringat 8 andversionat 0x24) matches ProsperoStore's caller, shadPS4, fpPS4 and OpenOrbis. These sources support the structure layout, but not the reported version value: the console firmware version remains unverified. The checks are unverified too: a null pointer returnsSCE_KERNEL_ERROR_EFAULTand asizeother than 0x28 returnsSCE_KERNEL_ERROR_EINVAL, while shadPS4 returns success for null and never readssize. - kern.rng_pseudo (libkernel) -
sysctlbynamefills the whole output buffer with bytes from the host'sstd::random_deviceand leaves the length unchanged; a write returns -1 withEPERMand a call without an output buffer throws. The only caller seen is mbedTLS'smbedtls_hardware_pollin the catalog's ProsperoLight boilerplate, which asks for 64-byte blocks and fails if fewer come back. The console's generator, its per-call maximum and its answer to a size query are unknown - kern.sdk_version (libkernel) -
sysctlbynamereports the system software version as the 4-byte value0x01000000(1.00), the valuesceKernelGetSystemSwVersionreports; a write returns -1 withEPERM. The major version is byte 3 and the minor version byte 2, in hex digits that read as decimal (13.60 is0x1360xxxx), as Capy Mobile (PPSA92280), remote_lua_loader and the lapse payload read it. Capy Mobile only displays it. The console's firmware version is not modeled and the low two bytes are unknown - sceKernelGetProsperoSystemSwVersion (libkernel) reports system software version
0x01000000("01.000.000"); the console's firmware version is not modeled. The 0x28-byte block (a 64-bit size at 0, the version string at 8 and the packed version at 0x24) follows SharpProspero, which Prospero Multi Tools (PPSA99110) and Prospero Explorer (PPSA99109) are built with and which sets the size to 40, and the same fields in etaHEN and shsrv. A size other than 0x28 returnsSCE_KERNEL_ERROR_EINVALwithout writing; whether the console checks the size is unverified, since etaHEN and shsrv declare a 0x30-byte block and do not set it - sceKernelGetAllowedSdkVersionOnSystem (libkernel) reports the system software version with the 12 patch bits set,
0x01000fff, as shadPS4 does on the PS4 and as SharpProspero describes it, which Prospero Explorer (PPSA99109) reads it through; a null pointer returnsSCE_KERNEL_ERROR_EINVAL. The console's value and its errors are unverified - getuid, geteuid, getgid, getegid and issetugid (libkernel) report the root identity (0) and a process that never changed credentials (
issetugid0), as a jailbroken process has; the host user and group are not exposed to the guest. The values a title sees on a console are unverified - sceKernelGetAppInfo (libkernel) - only
app_idand the title ID (offset 0x10, up to 9 characters plus a terminator) are written; callers declare the structure with different sizes, so the rest is left alone.app_idis 1, the running title's id in libSceSystemService, which is a guess, not something measured. The error codes follow shadPS4:EPERMfor another process, and 0 without writing anything for a null pointer. - AMPR object layout and compact gathers - the 24-byte object and offsets (type 0, cursor 4, count 8, capacity 12, pointer 16) follow ampr_emu assertions and its C declaration. AnyPS5 represents the 32-bit type word as low 16-bit type and high 16-bit recording flags. Command encoding is AnyPS5 internal: opcode 29 and three 32-bit words encode the high offset byte, length minus one and low offset word. The 12-byte size reduces HFW's 1 MiB buffer pressure; it is not a claim about console opcode encoding. Existing 40-bit offsets and lengths 1 through 2^32 are retained; console behavior outside those limits is unverified.
- APR resolve ForEach result (libkernel) -
sceKernelAprResolveFilepathsToIdsAndFileSizesForEachreturns the number of paths that resolved, with the per-path status inresultsand the failed ids/sizes set to the invalid id and 0. The ampr_emu bridge passes the count of its resolver through and does not show what is counted; counting successes is not confirmed on a title. The guest errno of the failing non-ForEachresolves is set through__error_nid_postfix - AMPR counter access (libSceAmpr) - signatures and checks of
WaitOnCounter_04_00,WriteCounter_04_00,ConstructNopandConstructMarkertaken from the ampr_emu reimplementation, which hands counter commands to the console and does not show their effect. The counters are taken as 32 bits each: the 8-byte access of counter n spans n (low) and n + 1 (high), the 2- and 1-byte accesses select a half or a byte of the counter by its offset, waits compare at the access width (signed and wrapped compares included), the AND mask applies to both sides and the atomic writes wrap within the access. TheConstructNoptype is not recorded - APR gather and scatter reads (libSceAmpr) - signatures, argument checks and the read cursor taken from the ampr_emu reimplementation, not confirmed on a title: each read leaves the file, the next file offset and the next destination; a gather reads that file at a new offset into the next destination, a scatter continues in the file into a new destination, a gather-scatter takes both. Recording one needs a read file since the last
ResetGatherScatterState; like ampr_emu,sceAmprCommandBufferResetkeeps that state, and a gather or scatter with no read before it in the submitted buffer throws instead of returningSCE_AMPR_ERROR_APR_INVALIDGATHERSCATTERSTATE - AMM map, map direct and unmap (libSceAmpr) - signatures and the protection mask (CPU, GPU, AMPR and ACP read and write) taken from the ampr_emu reimplementation, which hands the remaining checks and the mapping to the console kernel; the mapper model taken from PS5PCEM:
sceAmprAmmGiveDirectMemoryusage 1 gives the allocated direct memory to the pool plain maps take pages from, usage 0 only allocates it. Not confirmed on a title. The AMM virtual address ranges are a 32 GiB range and a 32 GiB multimap range reserved on first use at the top of the guest arena, above the addresses that maps withoutMAP_FIXEDare given lowest first and that titles derive their next hints from; the console's addresses are not known (ampr_emu takes them fromsceKernelMapperGetParam), and a reservation that cannot be made there throws. Maps outside them throw. Addresses, sizes and direct offsets must be 16 KiB aligned. The memory type and the GPU mask are ignored, AMPR and ACP access maps as CPU access, unmapped pages go back to the pool and stay reserved. Submission runs the buffer before returning, the submit result is always 0 and a failing command throws; the AMM measures return errors sign-extended, as ampr_emu does.sceAmprAmmGetVirtualAddressRangesthrows for a null output - AMM remap, multimap and protection changes (libSceAmpr) - signatures and the protection and mask checks taken from ampr_emu; the effects are inferred from the names, not confirmed on a title. A remap moves every page of a fully mapped range to the new address with the given protection and leaves the old range reserved; a multimap maps the same pages at a second address, anywhere in the AMM ranges, and a pool page goes back to the pool once its last mapping is unmapped; a multimap onto its own source range throws. A protection change sets the masked bits on every page of a fully mapped range; the memory type is recorded and ignored. A command on a range that is not fully mapped throws
- AMM PRT ranges (libSceAmpr) - signatures, checks and their order taken from ampr_emu, where
MapAsPrtis a map with the PRT flag and protection 0 andAllocatePaForPrta memory type and protection change with mask 1019, both checking the buffer memory after its size; the effects are inferred from the names, not confirmed on a title. Unbacked PRT pages are zero-filled pages with GPU read access, so CPU reads see zeros instead of faulting and GPU writes fault instead of being dropped.AllocatePaForPrtbacks each unbacked page with a pool page and sets the type and protection of backed ones;RemapIntoPrtmoves a fully mapped range into a PRT range, its opcode argument (1011 when 0, as in ampr_emu) is recorded and ignored;UnmapToPrtreturns the pages to the pool and zero-fills them again. A plain map, unmap or remap over a PRT range ends it;AllocatePaForPrt,RemapIntoPrtorUnmapToPrtoutside a PRT range throws - AMM kernel write commands (libkernel) - signatures of
sceKernelWriteModifyMtypeProtectCommandandsceKernelWriteRemapIntoPrtCommandtaken from ampr_emu's libkernel hook targets, which forward to the real kernel; the measure mode (dstnull reports the size,outSizenull skips the report) follows ampr_emu's measure-then-record calls, not confirmed on a title. The range, protection and mask checks mirror thelibSceAmprsiblings, and the recorded bytes match them exactly so the submitted buffer executes on the existing paths - sceCoredumpWriteUserString and sceSaveDataGetConvertProgress - imported by PPSA16064, not called during its start-up and added without an implementation; unknown signatures
- sceKernelInternalMemoryGetModuleSegmentInfo (libkernel) - the
(InternalSegmentInfo* result)signature, the 16-byte{address, size}result and the choice of the main program's first segment follow fpPS4 only, which fills it through itssceKernelGetLibkernelTextLocationfrom the first segment ofeboot.bin; whether the console reports that segment, the text of libkernel itself or the calling module's is unknown. The segment is the first onesceKernelGetModuleInforeports for the main program, and 0 is returned. A null result throws. 44 audited titles that bundle their ownlibc.prximport it; no call has been observed - sceKernelGetModuleInfoForUnwind (libkernel) - on Linux the tables come from
sceKernelGetModuleInfoFromAddr, whoseeh_frame_sizeincludes the zero terminator, as measured on firmware 13.60 (reported in #2419, not reproduced here); on Windows it is assumed to stop before the terminator. LLVM libunwind'sCFI_Parser::findFDEstops at the terminator or the length, whichever comes first, so it finds the same FDEs either way. Only the main executable and.guest.prximages report tables; other host images report none, as on Windows - sceKernelGetModuleInfoFromAddr (libkernel) - the 0x1A8-byte info layout follows the shadPS4 reimplementation; a title's
libc.prxreads onlyid(PPSA14632). The meaning offlagsis unknown; only 2 is accepted. The inputst_sizeis ignored, because PPSA21703'slibc.prxpasses an uninitialized 0x1A8-byte buffer; the full size is written back. The id is thesceKernelLoadStartModulehandle of an image opened through the loader and otherwise a stable id from the same range. The name is the host file name without.guest.prx. An image with more than 4 load segments (the converted executable has 7) reports its first 4.tls_offsetis 0 andref_countis 1, as the host loader exposes neither. On Windows the module is the PE image holding the address: a relinked image reports its.elfsections as segments and the eh_frame_hdr recorded in.ehmeta, any other image its first 4 sections with memory access and the.ehframsection without an eh_frame_hdr; the TLS fields andinit_proc_addr/fini_proc_addrare 0 - sceKernelGetModuleList (libkernel) - lists the main program and every loaded
.prximage in load order; host runtime libraries are left out. The handles are the idssceKernelGetModuleInfoFromAddrreports, not the console's. The(int32_t* handles, size_t count, size_t* actual)signature and returningENOMEMwithout writingactualafter filling the firstcounthandles when more images are loaded follow shadPS4; whether the console writes any handles in that case is unknown - sceKernelGetModuleInfo (libkernel) - the 0x160-byte layout (
st_size,name[256], 4 segments,segment_count,fingerprint[20]) follows fpPS4 and shadPS4. Only thatst_sizeis accepted, as in shadPS4; other sizes returnEINVAL, a null pointerEFAULTand a handlesceKernelGetModuleListdoes not listESRCH. Name and segments are the onessceKernelGetModuleInfoFromAddrreports, on Windows from the same PE sections, soprotuses the read/write/execute bits 1/2/4, while fpPS4 and shadPS4 store the ELFp_flags. The fingerprint is left zero, as the host image does not carry it - sceKernelGetModuleList2 and sceKernelGetModuleInfo2 (libkernel) - the title-module variants follow shadPS4:
sceKernelGetModuleList2lists whatsceKernelGetModuleListlists without system libraries, andsceKernelGetModuleInfo2answersEPERMfor a system library after theEFAULT,EINVALandESRCHchecks ofsceKernelGetModuleInfo. A system library here is a loaded.prximage that is not a relinked title module (.guest.prx); the main program and the title's own modules are listed. Not verified on the console. PPSA34063 imports both and fails to load without them - sceKernelGetLibkernelTextLocation (libkernel) - the
(void** address, std::size_t* size)signature and the choice of the main program's first segment follow fpPS4; whether the console reports that segment, the text of libkernel itself or the calling module's is unverified. The segment is the first onesceKernelGetModuleInforeports for the main program, and 0 is returned. A null argument throws. - sceKernelReleaseFlexibleMemory (libkernel) - unmaps the range like sceKernelMunmap, as fpPS4 and prosper do; whether the console keeps the virtual range reserved after releasing its pages is unverified
- sceKernelAvailableFlexibleMemorySize (libkernel) - the segments of the title's executable and of its
.guest.prxmodules count against the 448 MiB flexible budget while they are loaded, for this size and for the flexible maps, as shadPS4 maps every segment of a module outside its system module directory as flexible memory on the PS4. Counted are the segments the title's ELF gives permissions, each rounded to 16 KiB pages; not counted are segments without permissions, the relinker's own blocks (on Linux both are the read/write/executePT_LOADs, plus the header block at file offset 0; on Windows everything outside the.elfsections) and the host system libraries. The Linux image carries no marker for the relinker's blocks, so they are told apart by those flags and that offset only: a title segment that is writable and executable, or starts at file offset 0, is not counted. A module whose segments exceed what is left still loads, and the available size then reads 0; shadPS4 fails the segment map instead (memory.cpp returnsEINVAL, module.cpp asserts). Which segments the PS5 charges, its rounding, whether system modules use the title's budget and when an unload releases the charge are not measured. PPSA15508 subtracts the reported size and a 10 MiB module allowance from its own 448 MiB budget at start-up and stops when the result exceeds its 146 MiB code and data limit (#2883) - Memory protection bits 0x100 and 0x200 (libkernel) - taken as audio coprocessor (ACP) read and write, as in the KytyPS5 and etaHEN headers; the coprocessor work runs on the host CPU, so they grant host read and read/write access like the GPU bits
- _umtx_op (libkernel) -
UMTX_OP_WAIT,UMTX_OP_WAKE,UMTX_OP_WAIT_UINT,UMTX_OP_WAIT_UINT_PRIVATE,UMTX_OP_WAKE_PRIVATEandUMTX_OP_NWAKE_PRIVATEfollow FreeBSD 11's kern_umtx.c: a timeout whose size argument is at most 16 is a relativetimespec, a larger one an_umtx_time, and a wake of 0 or fewer wakes one waiter.UMTX_OP_NWAKE_PRIVATEreads the value as anintcount of pointers at the object and wakes every waiter on each one; a count of 0 or fewer reads nothing, and a null list fails withEFAULT, where FreeBSD'scopyinwould also fail for any other unreadable list. Waiters share the queue ofsceKernelSyncOnAddressWait. Operation 0 fails withEOPNOTSUPPand operations above 26 withEINVAL, as in FreeBSD 11;UMTX_OP_WAIT_UINTwith a value that does not fit in 32 bits returns 0 at once, as FreeBSD's zero-extended compare does. Operation 1 throws, since PPSA12544's call_once uses it in a way FreeBSD rejects; the other operations throw, and so does a misaligned object. PPSA12544'slibc.prxpassesUMTX_OP_WAITandUMTX_OP_WAIT_UINTa pointer to a 4-byte microsecond timeout with size argument 0, which FreeBSD reads as atimespec, and waits for a running call_once with operation 1; itsPS5Util.prxpasses atimespec. Whether the console reads a microsecond timeout there, and what operation 1 does on it, is unverified. A libc call cannot be told apart from atimespeccall by the size argument alone, so a timeout with size argument 0 is read as atimespecand only throws when it is not a valid one (negative seconds, nanoseconds outside [0, 1e9)), which is where FreeBSD would returnEINVAL; a microsecond value that happens to read as a validtimespecis waited on as one - sceKernelSyncOnAddressWait (libkernel) - the only known caller passes a null timeout and a name string as the fourth argument; the timeout is assumed to point to microseconds like the other kernel waits, and the name is ignored
- sceKernelSyncOnAddressWait8 / sceKernelSyncOnAddressWait16 / sceKernelSyncOnAddressWait32 / sceKernelSyncOnAddressWait64 (libkernel) - libc's
__std_atomic_wait_direct_8/16/32/64pass a microsecond timeout or null and ignore the result; the by-value comparand, return values and the 2- and 8-byte alignment of Wait16 and Wait64 are assumed - scePthreadRwlockDestroy, pthread_rwlock_destroy (libkernel) - measured on a PS5 (firmware 13.60): destroying a rwlock returns 0 whether it is free or held for reading or writing, and leaves 1 in the handle; every call on that handle then returns
EINVALuntil it is initialized again, and a zero handle is initialized on first use by thescePthreadRwlockcalls as by the POSIX ones. A rwlock destroyed while held is not freed, so its memory leaks. Destroying a rwlock while another thread is acquiring it is not guarded - scePthreadCondWait / scePthreadCondTimedwait (libkernel) - before waiting, FreeBSD libthr's
cond_wait_commonchecks ownership through_mutex_owned: an unowned mutex returnsEPERM, while its destroyed marker returnsEINVAL. An untouched adaptive static initializer (slot value 1) therefore returnsEPERM; the test covers this, an uninitialized slot, a mutex owned by another thread, and the destroyed marker for both timed and untimed sce and POSIX waits. A recursive mutex locked several times is released completely for the wait and relocked to the same depth afterwards, as FreeBSD libthr does (_mutex_cv_unlock,_mutex_cv_lock). These FreeBSD-derived behaviors remain unverified on console hardware - sceKernelAioSubmitReadCommandsMultiple / sceKernelAioSubmitWriteCommandsMultiple / sceKernelAioWaitRequests / sceKernelAioPollRequests / sceKernelAioCancelRequest / sceKernelAioCancelRequests / sceKernelAioDeleteRequests (libkernel) - behaviour from shadPS4 (one id per request for the Multiple submits, cancel turns any request aborted and id 0 reports processing, wait mode 2 returns once one request completed, poll copies every state without waiting); the 128 requests or ids per batch limit is from SharpProspero, with an unknown error, so larger batches throw; wait modes other than 1 (and) and 2 (or) throw; null pointers, negative counts and invalid ids return the codes the single-request siblings use, checked before any state is written
- scePthreadAttr setters and getters (libkernel) - measured on a PS5 (firmware 13.60): a null or uninitialized attribute returns
EINVAL, as does a null output of the stack size, detach state and scheduling parameter getters; a policy other than 1 and 3, an inheritance other than 0 and 4, or a priority outside 256 to 767 (or a null parameter) returnsENOTSUP(0x8002002D); a detach state other than 0 and 1 and a stack size below 16384 returnEINVAL; any affinity mask is accepted. A null attribute pointer toscePthreadAttrInitand a null output ofscePthreadAttrGetaffinitycrashed the payload, so they still throw. A new attribute holds a 64 KiB stack size on the console and 1 MiB here, which the host code that runs on guest threads needs - sceKernelGetAvailableCpumask (libkernel) - returns the default thread affinity, 0x1FFF (CPUs 0 to 12), as KytyPS5 does. Titles pin threads within it (PPSA02664 passes 0x1FFB, Hades II PPSA36082 0x3 and 0x3F); whether CPU 13 is available to a title is not confirmed
- sceKernelGetCurrentCpu (libkernel) - guest affinities are not applied to host threads, so the host CPU index is mapped into the calling thread's affinity clipped to
sceKernelGetAvailableCpumask(the available mask when they do not overlap): host CPU n reports the (n modulo the CPU count)-th CPU of that mask, so a thread pinned to one CPU reports that CPU, as a FreeBSDcpusetguarantees on the console. Which CPU the console reports for a thread allowed on several is not known; shadPS4 returns 0 - pthread_attr_setsolosched_np (libkernel) takes
(attr, int)and stores the value throughscePthreadAttrSetsolosched, returningEINVAL(22) for a null or uninitialized attribute like the other POSIX attribute setters. Only the name is public (aerolib2+pVfgiEd7A); the signature and behaviour follow the SCE twin, which KytyPS5 and sharpemu store as anintwithout a range check, and PS5PCEM implements this alias over it. On a PS5 (firmware 13.60) only 0 and 16 are accepted; every other value returnsENOTSUP(45,0x8002002Dfrom the SCE call) and keeps the stored one, and the SCE calls returnEINVALfor a null or uninitialized attribute. PPSA15878 passes 16. Threads created from the attribute are not scheduled differently; what solo scheduling does on the console is unknown. Returnal (PPSA01285 v03.000.005) stopped on it withwhat(): pthread_attr_setsolosched_np_nid_postfix not implemented(#2872, #1155); LEGO Horizon Adventures (PPSA14632, #734) and Palworld (PPSA23126, #2598) import it - sceKernelMapFlexibleMemory / sceKernelMapNamedFlexibleMemoryInternal (libkernel) - flag 0x8000 is accepted and ignored; its meaning is not established. KytyPS5 (
GUEST_MAP_UNKNOWN_8000) and sharpemu accept it without reading it. Every known caller is an SDK 9libc.prxheap, which passes it with read/write protection and uses the mapping as an olderlibc.prxusessceKernelMapNamedFlexibleMemorywith flags 0: through the Internal variant in Astro Bot PPSA21564, throughsceKernelMapFlexibleMemoryin Animal Well PPSA22520 01.000.011 - sceKernelMtypeprotect (libkernel) - sets the memory type of the direct mappings in the page-rounded range and of the direct memory behind them, as shadPS4 and prosper do (KytyPS5 ignores the type); the type is not validated, flexible pages in the range only get the protection, and a later map of the retyped direct memory reports the type it was allocated with.
sceKernelBatchMap2operation 4 takes the same path with the entry type - Map hints inside a reservation (libkernel) -
sceKernelMapDirectMemoryand the flexible and anonymous maps place a mapping withoutMAP_FIXEDat its hint address when the whole range lies in a range still reserved bysceKernelReserveVirtualRange, as ifMAP_FIXEDwere set. Taken from PPSA01474, which reserves 64 GiB and then maps its heaps inside it with hints and noMAP_FIXED, and uses the hint addresses afterwards; not measured on the console. Hints outside a reservation, or over a range that is partly mapped, stay hints - _sceKernelRtldThreadAtexitIncrement, _sceKernelRtldThreadAtexitDecrement (libkernel) - the argument is the
dsoaddress a title'slibc.prxpasses to__cxa_thread_atexit(PPSA14632), which fails when Increment returns nonzero. As in the fpPS4 reimplementation, Increment takes a reference on the loaded image containing the address and Decrement releases one; the variants without the leading underscore are assumed to match - tcgetattr, tcsetattr (libkernel) - every file and pipe descriptor is taken as not a terminal (
ENOTTY), and a socket getsEADDRNOTAVAILforAF_INETandEOPNOTSUPPotherwise, as FreeBSD'sin_controlandpru_control_notsuppanswer a termios ioctl; what descriptors 0 to 2 of a title are on the console, and whether any of them is a terminal there, is unknown - select (libkernel) - descriptor 0 is never reported readable and descriptors 1 and 2 are always writable, as for a console title with no input; reads from descriptor 0 still go to the host stdin.
/dev/randomand/dev/urandomare always readable and writable, as FreeBSD reports a seeded random device. Other descriptors that are not libSceNet sockets throw. Dungeons (PPSA16064) selects on descriptor 0 - select (libkernel) - a descriptor the socket poller reports as unknown that is below
GuestSockets::FirstDescriptoris polled on the host instead of throwing, except on Windows where it still throws; an invalid host descriptor fails withEBADF, and mixed host and socket sets are polled in short alternating slices so neither side waits out the full slice alone. Wobbly Life (PPSA29413) selects on file descriptors while streaming its bundles - __progname (libkernel) - unknown data export
- environ (libkernel) - data export pointing to a fixed empty environment so titles that import it load; it is not the environment libc's
getenvreads, so it lists none of those variables andsetenv/putenvchanges do not appear in it - seteuid, setegid, setuid, setreuid, setregid, setgroups, getgroups (libkernel) - the guest process is assumed to run as root, with real, effective and saved user and group ids 0. As in FreeBSD's
sys_seteuid,sys_setegid,sys_setuid,sys_setreuidandsys_setregid, id 0 (or -1 for an unchangedsetreuid/setregidid) is then accepted without a privilege check and changes no credential, so 0 is returned; any other id would change an id, which is not modelled, and throws.setgroupskeeps the supplementary group list askern_setgroupsdoes (NGROUPS_MAX1023, an empty list leaves the effective group as the only entry, a first entry other than 0 would change the effective group and throws) andgetgroupsreports it. The ids and privileges a title has on a console are unverified - pthread_barrierattr_setpshared (libkernel) - PTHREAD_PROCESS_SHARED is accepted on the assumption that the console follows FreeBSD 11.0 libthr, which accepts it (9.0 rejects it with EINVAL); unverified on hardware. Guest code runs in one process, so a shared barrier behaves as a private one
- pthread_getname_np (libkernel) - a thread that has already been joined returns
ESRCH(3) on a PS5 (firmware 13.60), but its object is freed after the join here, so the pointer cannot be told apart from a live thread and its name is read as for a live one - sceKernelGetOperationMode (libkernel) - the signature
(int* mode, int* submode)comes from PPSA12544, which logs both values after the call and ignores the result. A homebrew payload on a PS5 (firmware 13.60) reads mode 2 and submode 0, nothing else is written, and the result register holds no status, so the function is taken to return nothing. Whether a title process reads the same values is unverified. Null outputs throw - sceCoredumpAttachMemoryRegion, sceCoredumpAttachUserMemoryFile (libkernel) - both take
(uint32_t userValue, const void* mem, size_t size): for the first, the IDA type database of Orbital and the SharpProspero bindings agree; the second has only SharpProspero (the PS4 5.05 firmware does not export it, so Orbital has no entry) and is described there as attaching the region as an unnamed user file. Not confirmed on a title; the RED engine's PS4 crash handler (Vangaurd) calls the siblingsceCoredumpAttachMemoryRegionAsUserFile(999, buffer, bytes, name)from inside its handler. Attaching belongs inside the core dump handler, which the system runs on its own thread after the process stops (SharpProspero's remark, the RED engine's usage andSCE_COREDUMP_ERROR_NOT_IN_COREDUMP_HANDLER, "function was not called from registered core dump handler", in the Vita's SceCoredump error table, RivetDB). The handler is never invoked here, so every call is outside it and returns that error; nothing is recorded, as there is no dump to attach to. Its value0x81180003comes from shadPS4 (PS4), not confirmed on a PS5: fpPS4 hasNOT_REGISTERED0x81180001 andALREADY_REGISTERED0x81180002, shadPS4'scoredump_error.hhasNOT_IN_COREDUMP_HANDLER= 0x81180003, and the Vita table numbersPARAM0,NOT_REGISTERED1,ALREADY_REGISTERED2 andNOT_IN_COREDUMP_HANDLER3. Whether the console checks the region before the calling context is unknown, so a null, empty or wrapping region throws.userValueis not interpreted; SharpProspero names its bits 31 and 30 as truncation flags for the user file variants - sceKernelAddTimerEvent (libkernel) -
usecis taken as the period in microseconds; re-adding an existing timer keeps its pending expiration count and restarts the period from the time of the call, where FreeBSD 12+filt_timertouchclears pending expirations onEV_ADD;usec == 0fires on every wait. None of this is confirmed on a PS5 title - sceKernelWaitEqueue (libkernel) - a level-triggered user event (
sceKernelAddUserEvent) is reported at most once per call, as in FreeBSDkqueue_scan(sys/kern/kern_event.c), which re-queues a reported knote withoutEV_CLEARorEV_DISPATCHbehind the scan marker, and kevent(2), where several triggers do not produce several kevents. Not measured on a console. Events are scanned in list order and the list is not rotated, so whennumis smaller than the number of ready level events the later ones can starve, where FreeBSD moves a reported level knote to the tail. Several completions of one AMPR or VideoOut event within one call are returned as separate entries, where FreeBSD would aggregate them; the Orbis behaviour is unconfirmed - AC1FtjqMCL0 (libkernel) - unknown name, signature
- 0iEKNAvT600 (libkernel) - unknown name, signature
- 2cELEBPdYQ0 (libkernel) - unknown name, signature
- 5xYxiOtOccA (libkernel) - unknown name, signature
- 6W+shIH315Q (libkernel) - unknown name, signature
- 7ilObq815O4 (libkernel) - unknown name, signature
- 7iq7Hfs8HBk (libkernel) - unknown name, signature
- AMJZhpC+siY (libkernel) - unknown name, signature
- E9XkHowt+dY (libkernel) - unknown name, signature
- GADjreszOgM (libkernel) - unknown name, signature
- Giyg2xGrXDU (libkernel) - unknown name, signature
- KC3y21wrqzc (libkernel) - unknown name, signature
- Qb8wS4GZUsw (libkernel) - unknown name, signature
- aAQZSjb2fho (libkernel) - unknown name, signature
- pnz21I6VjDs (libkernel) - unknown name, signature
- qk043QPsrZU (libkernel) - unknown name, signature
- uDGXwUKqi8s (libkernel) - unknown name, signature
- sceKernelGetCpuTemperature (libkernel) - imported by PPSA99902, which fails to load without it; added without an implementation because its behavior is unverified.
- LinuxProtFromSce (libkernel) - protection bits 0x100 and 0x200 are accepted and assumed not to affect host CPU access; host protection is derived only from the read, write and execute bits
- sched_get_priority_max, sched_get_priority_min (libkernel) - measured on a PS5 (firmware 13.60):
SCHED_FIFO(1) andSCHED_RR(3) report a maximum of 767 and a minimum of 256, and every other policy,SCHED_OTHER(2) included, returns -1 withEINVAL.pthread_setschedparamignores the policy and does not check the priority, where the console rejectsSCHED_OTHERand priorities below 256 withEINVAL - inet_pton, inet_ntop (libkernel) - the text forms are assumed to be those of FreeBSD 11.4 and are unverified on a console:
inet_ptonaccepts only four decimal parts without leading zeros forAF_INETand the RFC 4291 forms forAF_INET6(one::standing for at least one group, a dotted-quad tail only as the last 32 bits, no zone id), andinet_ntopprints lowercase hex with the first longest run of two or more zero groups compressed, and a dotted tail only for::a.b.c.dand::ffff:a.b.c.d. They no longer depend on the host resolver library
Functional
- JIT shared memory (libkernel) -
sceKernelJitCreateSharedMemory,sceKernelJitCreateAliasOfSharedMemoryandsceKernelJitMapSharedMemorytake the signatures of Orbital'stools/ida/db_types.json(name, length, maximum protection, descriptor out; descriptor, maximum protection, descriptor out; descriptor, protection, address in and out), which ps4sdk, ps5-jar-loader and the call sites in RetroArch PPSA99169, XPSemu PPSA97358 and VLC PPSA85300 match; SharpProspero declares the alias as returning the descriptor. The object is a host anonymous file shared by its descriptors (amemfdon Linux, a delete-on-close temporary file mapped as an executable section on Windows), the alias is a duplicate descriptor, and every map maps the whole object, so writes through one view show through the others; a non-null address is a hint, as inmmapwithoutMAP_FIXED. Not measured on the console: a length that is zero or not a multiple of 16 KiB and protection bits other than CPU read, write and execute areEINVAL; an alias or a map asking for more than the descriptor's maximum protection (write and execute counting as read) isEACCES, as FreeBSD 11'svm_map_protecttreats a protection pastmax_protection; a descriptor that is not a JIT object isEBADF. The name is ignored, the objects do not count against the flexible memory budget,mprotectof a view is not limited to the maximum protection, andmmapof the descriptors is unsupported, as forshm_open. On Linux thememfdis created withoutMFD_EXEC, which Linux 6.3 added and older kernels reject withEINVAL, and relies on the protection of the mapping: the flag only sets the file's execute permission bits, and the direct memorymemfdis mapped executable the same way; a host withvm.memfd_noexecset to 2 refuses the creation and the call throws - kqueue and kevent (libkernel) follow FreeBSD 11's
kern_event.c(kqueue_kevent,kqueue_register,kqueue_scan, the timer and user filters) over the event queue; nothing is measured on a console. The descriptor is a host null device registered as the kqueue:closeandsceKernelCloseclose the queue anddup/dup2of it throw, butread,writeandfstatact on the null device instead of failing withEOPNOTSUPPor reportingS_IFIFO. Read and write events are supported on guest sockets only, plus the timer, user and vnode filters; other filters,EV_DISABLE,EV_DISPATCH,EV_FORCEONESHOT,NOTE_LOWAT,EV_CLEARon a socket,EVFILT_READon another kqueue, aNOTE_NSECONDSperiod above one second with a fraction (11.0 converts the fraction with the microsecond macro), any change to an existing timer (11.0 keeps the armed expiry and applies the new period after it, 11.4'sfilt_timertouchrestarts it) and a negativeneventsthrow. A new user event keeps itsfflagsunmasked and is not triggered byNOTE_TRIGGER, becausefilt_userattachreads the already clearedkn_fflags. The timer limitkq_calloutmax(ENOMEM) is not enforced, and closing a kqueue wakes a thread waiting on it inkeventwithEBADF, wherekqueue_drainmakes the close wait for that thread. A level-triggered event is reported once per call and moved behind the other events, as inkqueue_scan; thesceKernel*Equeuecalls keep their own collection loop - EVFILT_VNODE, sceKernelAddFileEvent and sceKernelDeleteFileEvent (libkernel) watch the host file or directory behind the descriptor and turn host changes into FreeBSD 11 vnode hints, which
filt_vfsvnodeadds whole when they share a bit with the requestedfflags: a write that grows a file isNOTE_WRITE | NOTE_EXTEND, another writeNOTE_WRITE, a shrinking truncate or an attribute changeNOTE_ATTRIB, a higher link countNOTE_LINK, a lower one or a pending deleteNOTE_DELETE, a new pathNOTE_RENAME; in a directory, an entry created, removed or renamed isNOTE_WRITE, withNOTE_LINKfor a subdirectory, and on Linux an entry moved from or to another directory addsNOTE_EXTEND; inotify queues the two halves of a rename one after the other, so a watcher woken by the first can read it alone, and a half read without the other is classified only after agetdents64on the watched directory, which takes the directory lock thatrenameholds until both halves are queued (do_renameat2aroundvfs_renameand itsfsnotify_move,iterate_dir), an ordering taken from the kernel source, not from inotify(7), which promises none; a directory registered withNOTE_EXTENDon Windows is accepted, asvfs_kqfilterdoes not check it, but never receives it, because the directory handle cannot tell a move between directories from a removal plus an addition. FreeBSD's hints depend on the filesystem and the console's filesystems are not known: a growingftruncatereportsNOTE_WRITE | NOTE_EXTENDwherevop_setattr_postreportsNOTE_ATTRIB, and on Windowsutimeson a file reportsNOTE_WRITE. Windows usesFindFirstChangeNotificationon the parent directory (and on a watched directory itself) and comparesGetFileInformationByHandleExsnapshots at least every 50 ms, because a write through an open handle is reported only when the handle is flushed or closed, so file hints can arrive 50 ms late; Linux uses inotify on the file and is not run.NOTE_REVOKE,NOTE_OPEN,NOTE_CLOSE,NOTE_CLOSE_WRITE,NOTE_READ, unknown bits and descriptors other than files, directories, pipes and sockets throw.sceKernelAddFileEvent(eq, fd, watch, udata)andsceKernelDeleteFileEvent(eq, fd)take the OpenOrbis and SharpProspero signatures;watchis taken as thefflagsand the event is added withEV_CLEAR, neither confirmed on a title - sem_timedwait (libkernel) consumes an available count before checking the timeout and waits indefinitely for a null timeout, following FreeBSD 11's
sem_timedwait. Console behavior for null and invalid timeouts when a count is available is unverified. - tcsendbreak, tcdrain, tcflush, tcflow, tcgetpgrp, tcsetpgrp (libkernel) follow FreeBSD 11.4's
termios.c:tcflushanswersEINVALfor a queue other thanTCIFLUSH,TCOFLUSHorTCIOFLUSHandtcflowfor an action outsideTCOOFF..TCIONbefore the descriptor is looked at, and every other call fails as its terminal ioctl does on a descriptor that is not a terminal, with the errorstcgetattrgives, sotcsendbreaknever reaches its 0.4 s pause. FreeBSD'spipe_ioctlanswersTIOCGPGRPandTIOCSPGRPon a pipe or FIFO with the descriptor's SIGIO owner, which is not modelled, sotcgetpgrpandtcsetpgrpthrow on a host pipe or FIFO above descriptor 2; descriptors 0 to 2 are taken as non-terminals that are not pipes, whatever the host attaches to them, so a pipe the guest creates on a freed descriptor 0 to 2 getsENOTTYthere. The PS5libkernelis assumed to use this FreeBSD code, andtcdrainis not a cancellation point here - Windows file timestamps use the host filesystem's timestamp range and resolution.
utimesandfutimesreject timestamps outside nonnegative signed 64-bit Windows file-time ticks withEINVAL, including exactly 1601-01-01 00:00:00 UTC, whose zero value means "leave unchanged" toSetFileTime. Guest directory descriptors still resolve through their recorded path. Filesystems with coarser timestamp resolution cannot retain every guest microsecond - Windows file identity (libkernel) -
statandfstatreport the volume serial number asst_devand the 64-bit file index folded into the guest's 32-bitst_ino(never 0), so two different files can in principle share anst_ino; the fold is not taken from a reference.st_nlinkis clamped to 65535, the width of the guest field. The call keeps the_wstat64values whenGetFileInformationByHandlefails - setitimer (libkernel) follows FreeBSD's
sys_setitimerandkern_setitimer:EINVALfor timers other thanITIMER_REAL,ITIMER_VIRTUALandITIMER_PROF, and for a value, or the interval of a non-zero value, with a negative field,tv_usecof 1000000 or more, or more thanINT32_MAX / 2seconds; a null value reads the timer asgetitimerdoes, withEFAULTwhen the output is null too.ITIMER_REALshares the timer thread ofalarm, which clears its interval: a zero value disarms it, the previous value is returned, and each expiry re-arms it byit_interval. An expiry delivers nothing: withSIG_IGNit is dropped, with the default disposition the process exits with status 142, and with a handler, or withSIGALRMblocked, it throws, since guestSIGALRMhandlers are never run and signals are never left pending. The value is not raised totick / 16asitimerfixdoes, and an interval below 1 ms throws, since the console'shz, and so that rounding, is unknown (1 ms covers anyhzof 63 or more).ITIMER_VIRTUALandITIMER_PROFthrow when armed, as process CPU time is not accounted, and read and disarm as zero. PPSA99420 imports it and fails to load without it - On Linux, direct memory lives in one sparse memfd at file offset = physical address, so the GPU imports can share one udmabuf buffer object per 64 MiB of it. Released direct memory is not punched out of the file, because a live import of its chunk pins the pages and the GPU would keep reading the old ones: its pages stay committed (the process keeps the high-water mark of the direct memory it used) and are zeroed when the range is allocated again.
- system (libkernel) runs no command. It follows FreeBSD 11's
lib/libc/stdlib/system.cfor a sandbox without/bin/sh: a null command returns 1 unconditionally, as that version does, and any command returns the wait status of a child that could not exec the shell and called_exit(127)(0x7f00). Whether the console's application sandbox has no shell, and whethervforksucceeds there (FreeBSD returns -1 when it fails), is unverified - sceKernelWriteThrottlingStatus (libkernel) reports no write throttling: the host SSD has no write budget, so the first qword of the 32-byte status is set to
UINT32_MAXand the rest is zeroed. PPSA17221 reads only that qword: it multiplies it by 64 KiB and compares the product with byte thresholds up to 0x4AF00000 to pick one of five tiers. When the call fails the title assumes 0x4B000001 bytes, which selects the same top tier asUINT32_MAX. What the value measures on hardware (a remaining budget or a rate) and the meaning of the other three qwords are unknown - Windows directory descriptors (libkernel) take one snapshot of the directory, on the first
getdents,getdirentriesor non-zerolseek(SEEK_SETorSEEK_CUR), and keep it until it is discarded;lseekto offset 0 only discards the snapshot, and the next read lists the directory again, so every rewind costs O(entries) on the next read.lseektakes the offset as an entry index andSEEK_CURwith offset 0 only reports the index.SEEK_ENDthrows, where the NUL descriptor used to return 0, because FreeBSD defines it relative to the directory size, which is not modelled. A negative result returnsEINVALand aSEEK_CURoffset that overflows returnsEOVERFLOW, as FreeBSDvn_seekreports them. Names whose UTF-8 encoding exceeds the one-byted_namlenlimit are not representable in this guest directory-record layout:getdentsreturnsENAMETOOLONGwithout consuming the entry. Repeated calls therefore report the same error and entries after that name cannot be reached through this descriptor; FreeBSD'sgetdentsbehavior for host filenames that exceed itsMAXNAMLENis not verified.getdirentriesstill reports 0 throughbasepinstead of the position of the block it read, so only 0 and values returned bylseekare valid offsets; FreeBSD offsets are filesystem cookies - /dev/random and /dev/urandom (libkernel) opened for reading return a descriptor backed by the host null device whose reads are filled with host OS entropy (
getentropy,rand_son Windows); both paths behave the same, never block, and positioned reads ignore the offset (FreeBSDrandom(4)). Only the exact paths are recognised,fstat,lseekandmmapsee the null device, and opening them for writing throws - pthread_attr_getinheritsched, pthread_attr_setinheritsched, pthread_attr_getscope, pthread_attr_setscope, pthread_attr_getstackaddr (libkernel) follow FreeBSD 11 libthr (thr_attr.c, thr_create.c), not measured on the console: the scope defaults to
PTHREAD_SCOPE_SYSTEM(2), only it andPTHREAD_SCOPE_PROCESS(0) are accepted and other values returnEINVAL, and an inherit value other thanPTHREAD_INHERIT_SCHED(4) orPTHREAD_EXPLICIT_SCHED(0) returnsENOTSUP.pthread_attr_getstackaddrreturns the configured stack address pointer (null by default). A null output ofpthread_attr_getinheritschedthrows, since libthr writes through it unchecked. A thread keeps the scope it was created with, taken from the creating thread underPTHREAD_INHERIT_SCHED, andpthread_attr_get_npandscePthreadAttrGetreport it, but every guest thread is a host thread at system scope, so process scope changes nothing - Shared memory (libkernel) on Linux implements anonymous and named objects, bounded descriptor writes and seeks, and
shm_unlinkwith effective read/write permission checks from FreeBSD 11. Named paths up to 1023 bytes use/anyps5-shm-plus SHA-1; collisions are not detected, and the namespace is shared across processes in the host mount namespace. Named creation applies the guest umask without changing the host mask. Linux procfs and/dev/shmare required. Operations use an advisory directory lock; external host operations bypass it, unrelated objects serialize, and descriptor operations require two spare host descriptors and compare device/inode with the initial descriptor identity on both the pinned-object and ordinary-file fallback paths. Guest mappings support shared and private mappings of these descriptors through the allocation tracker and pin a duplicate descriptor during validation and mapping; mapping requires one spare host descriptor; file-backed mappings use the write-watch scan fallback because aliases and descriptor writes bypass per-mapping tracking. Named objects and file-backed mappings on Windows remain unsupported. Invalid non-null name pointers, console behaviour and title compatibility remain unverified. - sceKernelAddReadEvent and sceKernelAddWriteEvent (libkernel): a write event reports the socket's send buffer size (
SO_SNDBUF) indata, not the free space left in it, as Windows has no query for that space. Only guest sockets are supported; other descriptors and a low watermark above 1 throw - close and setsockopt (libkernel) reach a libSceNet socket through hooks libSceNet registers, as
selectpolls them; the other libkernel socket calls do not. libSceNet numbers its sockets from 32 in its own table, so a CRT file descriptor and a socket can share a number;closethen closes the socket. On the console both are one kernel descriptor space - sceKernelPread, sceKernelPwrite, sceKernelPreadv, sceKernelPwritev (libkernel) on Windows transfer at the given offset with an overlapped
ReadFile/WriteFileand restore the descriptor's file pointer afterwards, so a concurrentread/writeon the same descriptor can see the moved pointer in between, unlike on the console. Handles that are not disk files returnESPIPE.readvon a pipe or console handle stops after the first iovec read, a short read the console is assumed to allow; each iovec is transferred separately, so a failure after the first transfer returns the bytes already done - sceKernelAioSubmitReadCommands, sceKernelAioSubmitWriteCommands and their Multiple variants (libkernel) on Windows transfer through the same positioned path as
sceKernelPread/sceKernelPwriteand restore the descriptor's file pointer afterwards, so a concurrentread/writeon the same descriptor can see the moved pointer in between, unlike on the console - sceKernelAioSetParam (libkernel) writes the five values into the 20-byte scheduling struct the first argument points to, following the declarations in Orbital, SharpProspero and ampr_emu. Whether the console checks the values is unknown, so a null struct, a scheduling window or delayed count limit outside 0..128, a split flag other than 0 or 1 and a split size or chunk size above 0x1000000 (SharpProspero's maximums) throw. The scheduling settings are not used:
sceKernelAioInitializeImplignores the struct and requests run synchronously on submit - sceKernelGetFsSandboxRandomWord (libkernel) returns a fixed directory name,
gkbHtXc3Wq. On the console the name is the process's randomized path (syscall 602,randomized_path), and the sandbox exposes system files under it, such ascommon/libandcommon/cert. Nothing is mounted under the name here, so/gkbHtXc3Wq/common/...resolves under the guest root like any other path and does not exist - getcontext and setcontext (libkernel) and makecontext (libSceLibcInternal) use FreeBSD 11's amd64
ucontext_t(mcontextat 0x10,mc_len800,uc_linkat 0x330,uc_stackat 0x338, 0x370 bytes), the layout homebrew built against FreeBSD's headers passes: PPSA99039's OpenSSLASYNC(crypto/async/arch/async_posix.c) captures into a 0x370-byte stack buffer.getcontextwrites the 0x330 bytes beforeuc_link, as FreeBSD'sUC_COPY_SIZE. The console's own layout for these functions is not verified; the exception handler's context is a different one (seesceKernelRaiseException) - getcontext and setcontext (libkernel) keep the 512-byte FXSAVE image in
mc_fpstate(x87, MXCSR, XMM0-15), so the upper halves of YMM0-15 are neither saved nor restored, andgetcontextleavesmc_xfpustateandmc_xfpustate_len0.getcontextsetsmc_fpformatandmc_ownedfpto FreeBSD's_MC_FPFMT_XMMand_MC_FPOWNED_FPU,mc_csandmc_ssto the host selectors, andmc_flags,mc_fsbaseandmc_gsbaseto 0.setcontextloadsmc_fpstatewhatevermc_fpformatandmc_ownedfpsay, and restores neither the segment selectors,mc_fsbaseandmc_gsbasenor the extended state, which FreeBSD restores whenmc_flagsasks for them - setcontext (libkernel) and longjmp (libc) on Windows set the thread's stack bounds in the TEB to the stack they switch to: a
makecontextstack, or else the committed region around the target stack pointer. A switch to any other guest stack, such as a context built by hand, gets the bounds of that region only - sceKernelInstallExceptionHandler records the handler, but a host fault still ends the process: only signals raised with
sceKernelRaiseExceptionare delivered. Unity's PS5Util module installs a SIGUSR1 handler that readsuc_mcontext.mc_rsp(offset 0xf8 of the context) and raises SIGUSR1 on other threads to stop them for garbage collection - sceKernelRaiseException on Linux sends the host SIGUSR1, which the library takes over, to the target thread, so the handler runs wherever the thread was interrupted, emulator code included. On the console kernel objects are system calls and libthr defers signals while a thread holds its internal locks; here a handler that needs a host lock the interrupted code holds deadlocks, and a thread that the handler keeps waiting keeps its host locks. Host waits resume after the handler. The host calls Linux does not restart end early: sleeps that do not retry return before their time, and the poll of
sceNetEpollWaitand socket calls with a send or receive timeout returnEINTRto the guest - sceKernelRaiseException builds the handler's
ucontextwith FreeBSD's amd64 layout (16-byte sigmask,mcontextat 0x40,mc_rspat 0xf8); the console's layout is not verified beyond the fields PS5Util reads - sceKernelRaiseException does not consult the target thread's signal mask
- pthread_sigmask (libkernel) shares the process-wide mask of
sigprocmaskand_sigprocmask, which keeps only the first 32 signals; FreeBSD keeps a mask per thread - sceKernelRaiseException reaches a thread that waits in an alertable
TimedWaitwait through an APC. A thread blocked anywhere else, including all waits underAPS5_COARSE_TIMED_WAITSand host waits inside the emulator, is redirected and runs the handler only when that wait returns - sceKernelRaiseException on Windows runs the handler wherever the target thread was interrupted. It waits only while the thread is inside winpthreads or restoring a context through
NtContinue, and throws if that lasts 1 s, so a handler that calls into other host code the thread was interrupted in, such as the C runtime's heap or a lock of the emulator, can deadlock on it or reenter it - sigaltstack (libkernel) records each thread's alternate signal stack and reports it back, following FreeBSD's
kern_sigaltstack(EINVALfor flags other thanSS_DISABLE,ENOMEMbelowMINSIGSTKSZ2048), but handlers never run on it, soSS_ONSTACKandEPERMare never reported - scePthreadJoin, scePthreadCreate (libkernel) - on a PS5 (firmware 13.60) joining a thread a second time returns
ESRCH(0x80020003); here a joined thread is released, so a second join reads freed memory. A null entry crashed the payload and still throws. Joining the calling thread returnsEDEADLKand a zeroed attribute creates a default thread, as on the console - Thread cancellation (libkernel) follows FreeBSD libthr (states and types 0/1 and 0/2,
PTHREAD_CANCELED1, the_pthread_cleanup_infonode layout), not measured on the console. A request is acted on only inscePthreadTestcancel, the condition variable,semandscePthreadSemwaits,scePthreadJoinand the sleeps, and their POSIX names; file and socket calls are not cancellation points. A sleep is not interrupted: the thread exits when it ends. The asynchronous type acts like the deferred one, except at the two set calls. - cpuset_setaffinity (libkernel) - only the calling thread or the calling process is handled. Bits outside
sceKernelGetAvailableCpumaskare dropped, and a mask with none of those bits fails withEDEADLK, as FreeBSD does when the new set has no CPU in common with the parent set - cpuset_getaffinity (libkernel) - only the calling thread or the calling process is handled. For the process the mask is the union of the affinities of the live guest threads, as FreeBSD 11.4 ORs the mask of every thread in the process; threads the guest did not create through libkernel are not included, and the console result is unverified
- dup and dup2 (libkernel) throw for the combinations they do not model:
dup2between a guest socket and a host descriptor in either direction. Guest sockets share one socket object between the duplicates and the descriptor numbers come from the guest socket counter, not the lowest free number as in FreeBSDkern_dup. The errno values for descriptor exhaustion are not verified against the console. - waitpid (libkernel) returns -1 with
ECHILD(EINVALfor unknown options): nothing here creates a child process; child processes would need a realwaitpid. - execv (libkernel) throws: replacing the process image is not supported, the same as
execvp. PPSA97358 imports it and fails to load without it. - kern.proc.pathname (libkernel) returns
/app0/eboot.binfor pid -1 and the calling process, following FreeBSD'ssysctl_kern_proc_pathname; the exact pathname on retail consoles remains unverified. - machdep.cacheline_size (libkernel) returns -1 with
ENOENT, matching FreeBSD amd64 where this sysctl OID is not defined. - getrlimit (libkernel) -
RLIMIT_CPU,RLIMIT_FSIZE,RLIMIT_CORE,RLIMIT_SBSIZE,RLIMIT_VMEM/AS,RLIMIT_NPTS,RLIMIT_SWAP,RLIMIT_KQUEUESandRLIMIT_UMTXPreport infinity as in FreeBSD's process-0 defaults, andRLIMIT_DATAmirrors the host limit.RLIMIT_STACK,RLIMIT_RSS,RLIMIT_MEMLOCK,RLIMIT_NPROCandRLIMIT_NOFILEthrow because no console values are established. - setrlimit (libkernel) validates the resource and input in FreeBSD order, maps negative limits to infinity, and lowers a soft limit above the hard limit. A request succeeds only when its normalized values match
getrlimit; changing limits throws because guest limit state is not stored. - execvp (libkernel) throws: replacing the process image is not supported. PPSA85300 imports it and fails to load without it; its
forkandvforkfail withENOSYS(libc_missing.c), so the child process that would call it is never created. - socketpair (libkernel) - the pair is the host's
AF_UNIXpair on Linux and, on Windows, a loopback TCP connection forSOCK_STREAMor two connected UDP sockets forSOCK_DGRAM;SOCK_SEQPACKETthrows on Windows. A datagram sent to a full receiver getsENOBUFSon the console, waits or getsEAGAINon Linux and is dropped on Windows, and on Windows a datagramrecvafter the peer closed reportsECONNRESETinstead of the console'sENOTCONN, and a streamsendafter the peer closed reportsECONNABORTEDinstead of the console'sEPIPE.readandwriteon a pair end go to the host like on every guest socket.getpeernameon a pair end succeeds after the peer closed, where the console returnsENOTCONN, andconnect,bindandsendtowith an address on a pair end report an address-family error instead of the console'sEISCONN. On Windowspollon a stream end reportsPOLLHUPwithoutPOLLINafter the peer'sshutdown(SHUT_WR)orclose, where the console reportsPOLLIN, withPOLLHUPonly afterclose - UDP recv/recvfrom and sceNetRecv/sceNetRecvfrom translate Windows WSAEMSGSIZE into the copied byte count for datagram sockets, including MSG_PEEK, and retain the sender address. This follows FreeBSD 11.4 recv(2) and Winsock's documented truncated-datagram behavior; console behavior and existing title impact are unverified.
- send, sendto (libkernel) - send and sendto without an address on an unconnected datagram socket map Windows
WSAENOTCONNto FreeBSD'sEDESTADDRREQ(39). - read, write and vector I/O (libkernel) on a guest socket use
recvandsendwithout flags;sceKernelReadvandsceKernelWritevgather or scatter through one socket operation, preserving stream short reads and datagram boundaries. The positionedpread,pwrite,preadvandpwritevforms, and theirsceKernelforms, returnESPIPEfor an open guest socket andEBADFfor a closed one. Guest socket descriptors start at0x10000000and are allocated upward, so the descriptor range selects the guest socket table or the host descriptor table.EPIPEfrom a write raises the host'sSIGPIPEon Linux, which the guest can neither ignore nor suppress:signal(SIGPIPE, SIG_IGN)andsigactionrecord the disposition, as they do for every number from 1 to 128, but only the six signals with host equivalents (2, 4, 6, 8, 11 and 15) take effect on the host or are delivered, so the hostSIGPIPEis not stopped;SO_NOSIGPIPEis not an option here, and raises nothing on Windows; awritelonger thanINT_MAXbytes isEMSGSIZEwhere the console sends it. AIO on a guest socket still goes to the host, which has no such descriptor - poll (libkernel) waits on guest sockets and pipes, through
WSAPollon Windows andpollon Linux; thepollfdlayout and flag values are FreeBSD's. A pipe follows FreeBSD'spipe_poll: the read end is readable when data is buffered, either end reportsPOLLHUPonce the other end is closed, with the requestedPOLLINandPOLLRDNORMbits and withoutPOLLOUT, whichpollscanclears, and the write end is writable whenPIPE_BUF(512) bytes are free on Windows, or when the host kernel says so on Linux.POLLOUTon a read end throws: FreeBSD opens both ends for reading and writing and reports it writable, and host pipes are one-way. Windows pipes cannot be waited on, so while a pipe is polledpollchecks it withNtQueryInformationFileand waits on the sockets in slices of 1 ms. A closed descriptor below the socket range reportsPOLLNVAL, and any other descriptor there (files, stdio) throws, as do event bits other thanPOLLIN,POLLPRI,POLLOUT,POLLRDNORM,POLLRDBANDandPOLLWRBAND(thePOLLERR,POLLHUPandPOLLNVALbits are ignored inevents),POLLPRIon Windows, whichWSAPollrejects, and an infinite timeout with no socket or pipe to wait on. A closed socket descriptor reportsPOLLNVAL; the console's limit on the descriptor count is unknown and not checked - Socket error numbers (libkernel) - a host socket error becomes the FreeBSD 11
errno.hnumber of the same name; the numbers are not checked on the console. WinsockWSAESHUTDOWNbecomesEPIPE, as a send aftershutdowndoes on FreeBSD, and a host error with no FreeBSD socket counterpart becomesEIO. A nonblockingconnectin progress reportsEINPROGRESSon Linux butEAGAINon Windows (WSAEWOULDBLOCK), where FreeBSD reportsEINPROGRESS. On Windows a refused nonblockingconnectis never reported (SO_ERRORis unsupported), so a repeated one keeps reportingEALREADYwhere FreeBSD reportsECONNREFUSED. A receive aftershutdown(SHUT_RD)reportsEPIPEon Windows where FreeBSD returns 0 - connect to AF_UNSPEC (libkernel) dissolves a datagram association as FreeBSD 11.4's
udp_disconnect()does, which resets the local address to the wildcard address and keeps the port. On Linux a socket bound to an explicit port keeps its local address as well (127.0.0.1:<port>stays127.0.0.1:<port>), because a bound socket cannot be bound again; one bound to port 0 is bound again to the wildcard address with the port it had - msync (libkernel) follows FreeBSD 11's
kern_msyncandvm_map_sync, not measured on the console: the address is rounded down to the page, a range that wraps isEINVAL, as isMS_ASYNCwithMS_INVALIDATE, and a range whose start or any page is not mapped (assceKernelVirtualQueryreports it, reservations included) isENOMEM; a page unmapped from inside a larger mapping still counts as mapped there, sincesceKernelVirtualQuerykeeps reporting the whole mapping. The guest has no file mappings, so a successful call writes nothing back.MS_INVALIDATEon a mapped range throws: FreeBSD returnsEBUSYwhen the range holdsmlocked pages, and locked pages are not tracked - sigtimedwait (libkernel) waits on a process-wide pending set instead of throwing: a signal raised while blocked stays pending and is taken by
sigwait,sigwaitinfoorsigtimedwait, delivered to the handler when_sigprocmaskunblocks it, or delivered bypause. The set covers all 128 signals and the lowest number that is pending and in the set is selected (FreeBSD specifies the lowest number only among real-time signals). Selection,EAGAINon timeout,EINVALfor atv_nsecoutside 0 to 1000000000 while nothing is pending andNULLtimeout blocking indefinitely follow FreeBSD's sigtimedwait(2).sigwaitreturns 0 with the number in its output, as POSIX specifies, andsigwaitinfoandsigtimedwaitreturn the number, as FreeBSD does. The guestsiginfo_tfollows FreeBSD 11'ssys/sys/siginfo.h: 80 bytes,si_signoat 0,si_codeat 8,si_pidat 12,si_uidat 16,si_addrat 24,si_valueat 32 andsi_bandat 40; onlysi_signo,si_code(SI_USER) andsi_pid(the guest pid) are written,si_uidstays 0 because no uid is modelled, and the console's layout is not verified. PPSA85300 importssigtimedwaitand fails to load without it; its only call site is VLC'svlc_writev(filesystem.c), which polls with a zero timeout to drain aSIGPIPEonly afterwritevfails withEPIPE. The waits are not cancellation points and an unblocked caught signal does not interrupt them withEINTR, where FreeBSD'ssigwaitinfoandsigtimedwaitmay return it.SIGPIPEhas no host equivalent and is never raised by a host write here (seeread, write and vector I/O), so VLC's drain finds nothing - pause, sigwait, sigwaitinfo (libkernel) take the pending set of
sigtimedwaitinstead of throwing.pausewaits for a pending signal that is not blocked and whose disposition can be delivered, runs its handler on the calling thread and returns -1 withEINTR; an ignored signal is discarded and the wait continues, and it never returns for a signal whose handler cannot run. A signal whose registered handler hasSA_SIGINFOstill throws, and one whose disposition is the default action and that has no host equivalent (every signal except 2, 4, 6, 8, 11 and 15) is neither delivered nor discarded: it stays pending until a wait takes it, where FreeBSD runs the default action, which terminates the process for most of them. PPSA68091, PPSA99169, PPSA99420 and PPSA97358 import them and fail to load without them. PPSA68091 callspauseat one site (0x8F7266), in a loop that waits while a global holds another thread'serrnoaddress. PPSA99169 only stores the address ofpausein a table of symbol addresses (0x30DB1). PPSA99420 callspauseat 0x3BD80F6 and 0x3C9E220,sigwaitat 0x3C9E4C7 andsigwaitinfoat 0x3C9E588. PPSA97358 callssigwaitfrom QEMU'ssigwait_compatthread (compatfd.c), whichqemu_signal_init(main-loop.c) starts forSIGIO,SIGALRMandSIGBUSwhen the main loop is created, so it reaches the wait at start-up, and from the vCPU thread of the dummy accelerator (dummy-cpus.c). None of the four waits is a cancellation point - getsid (libkernel) returns the calling process ID for pid 0 and the calling process, and
ESRCHfor other process IDs, assuming the single guest process is its own session leader. PPSA74126 imports it and fails to load without it - sigaction (libkernel) records the handler, flags and mask of every signal from 1 to 128 and reports them back, following FreeBSD's
sigaction(EINVALfor other signals, and for a handler onSIGKILLorSIGSTOP);signalrecords its handler withSA_RESTART, as FreeBSD's libc does. Only handlers withoutSA_SIGINFOon the signalssignalalready delivers (SIGINT,SIGILL,SIGABRT,SIGFPE,SIGSEGV,SIGTERM) run, the same waysignalhandlers do; their mask and flags are not applied.SA_SIGINFOhandlers are recorded but never called, since that needs FreeBSD'ssiginfo_tanducontext_t, and neither are the handlers of other signals (SIGBUS,SIGHUP, ...), whether they are set bysigactionor bysignal, which records them too (every number from 1 to 128, withSA_RESTARTand an empty mask replacing whatsigactionstored;SIGKILLandSIGSTOPaccept only the default handler in both calls, as in FreeBSD'skern_sigaction).raiseandkillaccept every number from 1 to 128 now: a blocked one stays pending on the set ofsigtimedwait, an unblocked one whose handler is registered runs it on the calling thread, and an unblocked one that has no host equivalent and no handler still fails withEINVAL, where FreeBSD runs its default action.raiseof anSA_SIGINFOhandler still throws instead of terminating - kill, killpg (libkernel) follow FreeBSD's
kern_killandkillpg1for the only guest process:EINVALfor signals outside 0 to 128 and for negativekillpgprocess groups, signal 0 only checks that the target exists, and its own pid, 0 and minus its own pid (the guest is taken to lead its own process group) signal it throughraise, so they shareraise's limits above. Any other pid, and -1, which skips the caller, reportESRCH, soEPERMis never reported - sceKernelFcntl (libkernel) runs the POSIX
fcntlbelow and returns its guest errno asSCE_KERNEL_ERROR_*, the form the othersceKernelfile exports use. The return values and error codes are unverified on a console - fcntl (libkernel) follows FreeBSD 11.4's
kern_fcntlandkern_dupon file, directory, pipe and character device descriptors; a socket keeps the libSceNet path (F_GETFL,F_SETFLwithO_NONBLOCK,EINVALfor every other command,F_GETFDandF_SETFDincluded). The close-on-exec flag and the status flags live in a guest table, the status flags shared bydup,dup2andF_DUPFDas in an open file description; a descriptor the table has not seen, such as 0 to 2, starts from the host's flags, since the console's are not known.F_GETFLtakes the access mode from the host (the granted access of the handle on Windows), so pipe ends reportO_RDONLYandO_WRONLYwhere FreeBSD's bidirectional pipes reportO_RDWR.F_DUPFDandF_DUPFD_CLOEXECreturn the lowest free host descriptor at or above the start, so the bound is the host table (EMFILEon Windows,EINVALpastRLIMIT_NOFILEon Linux), not the console's unknownRLIMIT_NOFILEandkern.maxfilesperproc.O_NONBLOCKswitches a host pipe (PIPE_NOWAITon Windows, where an empty read and a full write then reportEAGAIN) and is only recorded on files, directories and the random device, as their reads never block; on a Windows console or other character device it throws. ChangingO_APPENDon a Windows file, changingO_FSYNCon a file,O_ASYNCon a pipe or character device (SIGIOis not delivered),F_GETOWN,F_SETOWNandF_SETLK_REMOTEthrow;O_DIRECT,F_RDAHEADandF_READAHEADare recorded as the hints they are. Record locks (F_GETLK,F_SETLK,F_SETLKWand their forms withoutl_sysid) use the host's POSIX locks on Linux and throw on Windows, andF_GETLKwithF_UNLCKthrows. The return values and error codes are unverified on a console - ioctl, _ioctl (libkernel) handle only
FIONBIOandFIONREADon a socket, and any other request there fails withENOTTY. On the other descriptors they follow FreeBSD'skern_ioctl,vn_ioctlandpipe_ioctl:FIONBIOsetsO_NONBLOCKasfcntldoes, andFIONREADreports the size past the offset of a file, the queued bytes of a pipe's read end, 0 on its write end andENOTTYon the random device, while it throws on a directory or another character device. Every termios request (groupt,TIOCGWINSZincluded) fails withENOTTY, since those descriptors are taken as not a terminal, as intcgetattr, and any other request throws. Stremio Plus (PPSA74126) imports_ioctlfor its statically linkedtc*functions, which sendTIOCGETA,TIOCSETA,TIOCSPGRPand the other termios requests - sendfile (libkernel) follows FreeBSD 11's
sendfilefor a connected stream socket: headers, the file fromoffset(to its end whennbytesis 0) and trailers, the file offset left unchanged,EAGAINwith*sbytesset after a partial send on a non-blocking socket. It reads the file throughsceKernelPreadin 64 KiB blocks and sends each withsend. A socket as the file fails withEINVAL, as on FreeBSD, but any other descriptorsceKernelPreadreads, such as/dev/urandom, is sent where FreeBSD requires a regular file or shared memory, and a file descriptor as the socket fails withEBADF, as forsend, where FreeBSD answersENOTSOCK.flagsare ignored: reads complete before sending, soSF_NODISKIOnever fails withEBUSY, andSF_SYNCreturns once the data is queued on the socket rather than sent. PS5MC (PPSA99420) imports it - pthread_kill (libkernel) returns the error number like FreeBSD's
pthread_kill:EINVALfor signals outside 0 to 128 andESRCHfor a null thread. Signal 0 reports any other thread handle as existing, without checking that the thread is still alive. A signal to the calling thread goes throughraise, so it sharesraise's limits; a signal to another thread is left on the pending set for whichever thread waits for or unblocks it, since it is not delivered to the chosen thread, and a handle that is not a live guest thread returnsESRCHwithout touching it - select (libkernel) validates
tv_usecbut saturates a valid timeout beyond the remainingsteady_clockrange attime_point::max(), so the wait can continue effectively indefinitely. The console's behavior for a valid timeout outside the host clock's range is unknown. - _fstatfs (libkernel) fills the FreeBSD 11
struct statfsof the PS5 payload SDK with the host volume that holds the file: block size, transfer size, total, free and available blocks, maximum name length and the read-only,nosuidandnoexecflags (on Windows only read-only, andf_filesandf_ffreeare 0, as NTFS has no fixed number of files). The filesystem type number and name, mount paths, owner, filesystem id and I/O counters are left 0 or empty, since they would describe a host mount, not a console one. Sockets and pipes returnEINVAL, as FreeBSD'sgetvnodedoes; a Windows descriptor that is neither a file nor a pipe throws. Stremio Plus (PPSA74126) reads the free space before a download and only logs the other fields - pthread_spin_init, pthread_spin_destroy, pthread_spin_lock, pthread_spin_trylock, pthread_spin_unlock (libkernel) follow FreeBSD 11.4 libthr
thr_pspinlock.cand the owner checks of itsthr_umtx.h, unverified on the console:EINVALfor a null or destroyed lock and apsharedother than 0 or 1,EBUSYfromtrylockwhile any thread holds it,EPERMfromunlockby a thread that does not hold it.PTHREAD_PROCESS_SHAREDallocates a private lock, as guest code runs in one process. libthr spins forever when the holder locks again; here that call throws - sceKernelGetEventError (libkernel) returns the event's
dataas anintwhenEV_ERROR(0x4000) is set inflagsand 0 otherwise, as KytyPS5 does and as FreeBSD 11's kevent reports a failed change (flags = EV_ERROR, errno indata). fpPS4 instead returnsfflagsplus0x80020000whenfflagsis nonzero. Whether the console readsdataorfflagsand returns the raw errno or an SCE error code is unverified. No event delivered by the equeue here carriesEV_ERROR, so the call returns 0 for every eventsceKernelWaitEqueuereports - pthread_cond_reltimedwait_np (libkernel) takes
(cond, mutex, usec), a relative timeout in microseconds, and isscePthreadCondTimedwaitwith POSIX error numbers. FreeBSD 11.4 has no such function; the signature comes only from shadPS4, which registers one function for this NID and forscePthreadCondTimedwait(condvar.cpp). shadPS4 reads a 64-bit count; here it is the 32-bitSceKernelUsecondsof the SCE twin, as forsem_reltimedwait_np. Unverified on the console - sysctl kern.arandom (libkernel) serves FreeBSD 11's MIB {1, 37} (CTL_KERN, KERN_ARANDOM) and the "kern.arandom" sysctlbyname lookup through std::random_device, returning min(*oldLength, 256) random bytes. Following FreeBSD's sysctl_kern_arnd, a null buffer reports min(*oldLength, 256) without writing, a null length returns 0 without writing, and requests with a new value return EPERM (1) as the node is read-only. Cryptographic quality depends on the host's random device implementation.
- sceKernelGetPageTableStats (libkernel) - reports 2048 page-table entries on each side (a 4 GiB pool of 2 MiB entries, the constants of KytyPS5) and all of them available: no entries are counted as used, so a title never sees page-table pressure. KytyPS5 counts the 2 MiB entries of the committed CPU- or GPU-accessible ranges as used, which this port does not do. The four
int*arguments follow OpenOrbis'libkernel.h, the Orbital type database and SharpProspero; a null pointer returnsSCE_KERNEL_ERROR_EFAULTas in KytyPS5. None of the values is measured on a console. PPSA30601 (Resonance) calls it during start-up