Standardize ValidPte setup across architectures
All checks were successful
Builds / ExectOS (amd64, release) (push) Successful in 24s
Builds / ExectOS (i686, release) (push) Successful in 26s
Builds / ExectOS (i686, debug) (push) Successful in 39s
Builds / ExectOS (amd64, debug) (push) Successful in 40s

This commit is contained in:
2026-01-14 22:42:14 +01:00
parent 0f38d39705
commit 7da6bcc75e
3 changed files with 15 additions and 30 deletions

View File

@@ -112,21 +112,6 @@ MM::Pte::InitializePageTable(VOID)
MM::Pte::MapPDE(MemoryLayout->SystemSpaceStart, (PVOID)MM_HIGHEST_SYSTEM_ADDRESS, &TemplatePte);
}
/**
* Initializes the system's PTE.
*
* @return This routine does not return any value.
*
* @since XT 1.0
*/
XTAPI
VOID
MM::Pte::InitializeSystemPte(VOID)
{
/* Initialize the PTE template */
ValidPte = {{MM_PTE_VALID|MM_PTE_EXECUTE_READWRITE|MM_PTE_DIRTY|MM_PTE_ACCESSED}};
}
/**
* Maps a range of virtual addresses at the PPE (Page Directory Pointer Entry) level.
*