STL1teandClaude Opus 5.5 b7eaabbc1e feat(kernel): share direct memory mapped at two addresses read-only ...

A title maps physical pages at a new address while the GPU still reads them
through the old one. Every view of such a page gets the same contents and
loses write access while the page is shared; the last view left gets its
protection back. A CPU write to a shared page faults, and views that differ
when one is unmapped (a GPU write through an import) throw, instead of the
views silently diverging.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-09-29 21:22:17 +03:00

..

DirectMemory.cpp

feat(kernel): share direct memory mapped at two addresses read-only

2026-09-29 21:22:17 +03:00

DirectMemory.hpp

feat(kernel, libc): memory, files and threads for retail title boot

2026-09-29 21:22:13 +03:00

Export.cpp

feat(kernel, libc): memory, files and threads for retail title boot

2026-09-29 21:22:13 +03:00

MemoryPool.cpp

feat(kernel, libc): memory, files and threads for retail title boot

2026-09-29 21:22:13 +03:00

MemoryPool.hpp

feat(kernel, libc): memory, files and threads for retail title boot

2026-09-29 21:22:13 +03:00

MemoryPoolExport.cpp

refactor: apply naming conventions and drop extern-C comment

2026-09-29 04:20:28 +03:00

PosixMemory.cpp

feat(kernel): support private anonymous guest memory mappings

2026-09-25 06:06:31 +10:00