summaryrefslogtreecommitdiffstats
path: root/src/core/hle/kernel/vm_manager.h (unfollow)
Commit message (Collapse)AuthorFilesLines
2018-11-18ldr_ro: Add error check for memory allocation failureZach Hilman1-1/+2
2018-11-13kernel/process: Migrate heap-related memory management out of the process class and into the vm managerLioncash1-0/+15
Avoids a breach of responsibilities in the interface and keeps the direct code for memory management within the VMManager class.
2018-10-26Kernel/Memory: Added a function to first a suitable guest address at which to allocate a region of a given size.bunnei1-0/+8
2018-10-18svc: Add missing sanitizing checks for MapSharedMemory/UnmapSharedMemoryLioncash1-0/+3
Now that the changes clarifying the address spaces has been merged, we can wrap the checks that the kernel performs when mapping shared memory (and other forms of memory) into its own helper function and then use those within MapSharedMemory and UnmapSharedMemory to complete the sanitizing checks that are supposed to be done.
2018-10-15svc: Clarify enum values for AddressSpaceBaseAddr and AddressSpaceSize in svcGetInfo()Lioncash1-0/+12
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.
2018-09-25svc: Report correct memory-related values within some of the cases in svcGetInfo()Lioncash1-9/+6
Previously, these were reporting hardcoded values, but given the regions can change depending on the requested address spaces, these need to report the values that the memory manager contains.
2018-09-25memory: Dehardcode the use of a 36-bit address spaceLioncash1-0/+3
Given games can also request a 32-bit or 39-bit address space, we shouldn't be hardcoding the address space range as 36-bit.
2018-09-24process/vm_manager: Amend API to allow reading parameters from NPDM metadataLioncash1-2/+82
Rather than hard-code the address range to be 36-bit, we can derive the parameters from supplied NPDM metadata if the supplied exectuable supports it. This is the bare minimum necessary for this to be possible. The following commits will rework the memory code further to adjust to this.
2018-09-15Port #4182 from Citra: "Prefix all size_t with std::"fearlessTobi1-2/+2
2018-08-02kernel/vm_manager: Use const where applicableLioncash1-4/+4
Makes our immutable state explicit.
2018-04-27core: Replace usages of LOG_GENERIC with new fmt-capable equivalentsLioncash1-1/+1
2018-03-16svc: Use more correct values for GetInfo MapRegion and NewMapRegion.bunnei1-9/+0
2018-03-16MemoryState: Add additional memory states and improve naming.bunnei1-10/+19
2018-01-27memory: Replace all memory hooking with Special regionsMerryMage1-3/+3
2018-01-19svc: Fix svcGetInfo MapRegionBaseAddr.bunnei1-0/+3
2018-01-03vm_manager: Use a more reasonable MAX_ADDRESS size.bunnei1-5/+4
2018-01-01vm_manager: Stub out a bunch of interfaces used by svcGetInfo.bunnei1-0/+18
2017-10-20hle: Fix QueryMemory response for MemoryInfo.bunnei1-11/+8
2017-09-30core: Various changes to support 64-bit addressing.bunnei1-10/+10
2017-09-10Kernel/Memory: Give each Process its own page table.Subv1-1/+5
The loader is in charge of setting the newly created process's page table as the main one during the loading process.
2017-05-25Kernel: Centralize error definitions in errors.hYuri Kunde Schlesner1-8/+0
2016-09-21Remove empty newlines in #include blocks.Emmanuel Gil Peyrot1-2/+0
This makes clang-format useful on those. Also add a bunch of forgotten transitive includes, which otherwise prevented compilation.
2016-09-18Sources: Run clang-format on everything.Emmanuel Gil Peyrot1-10/+11
2016-01-30Memory: Implement MMIOMerryMage1-1/+4
2015-08-16Kernel: Properly implement ControlMemory FREE and COMMITYuri Kunde Schlesner1-3/+21
2015-08-16VMManager: Introduce names for used ResultCodesYuri Kunde Schlesner1-0/+8
2015-08-16VMManager: Make LogLayout log level configurable as a parameterYuri Kunde Schlesner1-1/+1
2015-08-16VMManager: Change block offsets to size_tYuri Kunde Schlesner1-2/+2
2015-07-12Core: Properly configure address space when loading a binaryYuri Kunde Schlesner1-1/+5
The code now properly configures the process image to match the loaded binary segments (code, rodata, data) instead of just blindly allocating a large chunk of dummy memory.
2015-06-28Core: Cleanup core includes.Emmanuel Gil Peyrot1-1/+0
2015-05-27Kernel: Add VMManager to manage process address spacesYuri Kunde Schlesner1-0/+200
This enables more dynamic management of the process address space, compared to just directly configuring the page table for major areas. This will serve as the foundation upon which the rest of the Kernel memory management functions will be built.