mirror of
https://github.com/yuzu-emu/yuzu-android.git
synced 2024-10-23 20:25:52 +02:00
90f8474fc1
So, one thing that's puzzled me is why the kernel seemed to *not* use the direct code address ranges in some cases for some service functions. For example, in svcMapMemory, the full address space width is compared against for validity, but for svcMapSharedMemory, it compares against 0xFFE00000, 0xFF8000000, and 0x7FF8000000 as upper bounds, and uses either 0x200000 or 0x8000000 as the lower-bounds as the beginning of the compared range. Coincidentally, these exact same values are also used in svcGetInfo, and also when initializing the user address space, so this is actually retrieving the ASLR extents, not the extents of the address space in general. |
||
|---|---|---|
| .. | ||
| arm | ||
| crypto | ||
| file_sys | ||
| frontend | ||
| gdbstub | ||
| hle | ||
| loader | ||
| tracer | ||
| CMakeLists.txt | ||
| core_cpu.cpp | ||
| core_cpu.h | ||
| core_timing_util.cpp | ||
| core_timing_util.h | ||
| core_timing.cpp | ||
| core_timing.h | ||
| core.cpp | ||
| core.h | ||
| memory_hook.cpp | ||
| memory_hook.h | ||
| memory_setup.h | ||
| memory.cpp | ||
| memory.h | ||
| perf_stats.cpp | ||
| perf_stats.h | ||
| settings.cpp | ||
| settings.h | ||
| telemetry_session.cpp | ||
| telemetry_session.h | ||