From 5a455c97def0ed5da665e83a1ea1802a48ff77d4 Mon Sep 17 00:00:00 2001 From: Stephen Miller Date: Fri, 9 May 2025 20:43:00 -0500 Subject: [PATCH] Remove phys_base modifications This can be handled later. Doing the logic properly would likely take work in MergeAdjacent, and would probably need to be applied to normal dmem mappings too. --- src/core/memory.cpp | 3 --- 1 file changed, 3 deletions(-) diff --git a/src/core/memory.cpp b/src/core/memory.cpp index 9746da533..fe9400604 100644 --- a/src/core/memory.cpp +++ b/src/core/memory.cpp @@ -310,9 +310,6 @@ int MemoryManager::PoolCommit(VAddr virtual_addr, size_t size, MemoryProt prot) return ORBIS_KERNEL_ERROR_EINVAL; } - // Before mapping, the reserved VMA should have it's physical base incremented. - vma.phys_base += size; - // Carve out the new VMA representing this mapping const auto new_vma_handle = CarveVMA(mapped_addr, size); auto& new_vma = new_vma_handle->second;