Developer knowledge network · moderated exchange

Społeczność UnreliableCode

Badania programistów, inżynieria wsteczna i społeczność programistów

Knowledge indexNa żywo
4Categories
919Threads
2.8KPosty
Tutorial

Physical Memory Page Mapping via MmMapIoSpace and PML4 translation [v2.4 Technical Discussion]

kernel_komrade
Driver Dev
MEMBER
Rozpustnik: 145
Data dołączenia: Feb 2019
Posty: 26
Dzięki: 45
1 miesięcy temu · Jul 8, 2026 2:21 AM
#1

To read physical RAM without relying on virtual page table CR3 contexts:

C
NTSTATUS ReadPhysicalAddress(PHYSICAL_ADDRESS physAddr, PVOID buffer, SIZE_T size) {
    PVOID pMapped = MmMapIoSpace(physAddr, size, MmNonCached);
    if (!pMapped) return STATUS_INSUFFICIENT_RESOURCES;
    RtlCopyMemory(buffer, pMapped, size);
    MmUnmapIoSpace(pMapped, size);
    return STATUS_SUCCESS;
}

Physical addresses are immutable across thread context switches, making physical memory mapping 100% immune to virtual CR3 directory base swapping.

dma_ghost
DMA Guru
MEMBER
Rozpustnik: 115
Data dołączenia: Jan 2020
Posty: 12
Dzięki: 83
1 miesięcy temu · Jul 8, 2026 6:40 AM
#2

This is identical to how PCIe DMA hardware reads memory. Physical RAM mapping is the cleanest kernel read technique.

hypervisor_hank
Kernel Wizard
MEMBER
Rozpustnik: 108
Data dołączenia: Feb 2020
Posty: 17
Dzięki: 44
1 miesięcy temu · Jul 8, 2026 10:37 AM
#3

Make sure you don't map non-existent physical addresses to avoid BugCheck 0x3B.