ShuriZma
/
xenia-canary
mirror of https://github.com/xenia-canary/xenia-canary.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Moving the physical heap up a bit to avoid overwriting 0x0.

This commit is contained in:
Ben Vanik 2013-10-21 23:56:16 -07:00
parent f676333ef0
commit 725cde55d4
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/xenia/core/memory.cc
View File

@ -71,7 +71,7 @@ DEFINE_uint64(
* this.
*/
#define XE_MEMORY_PHYSICAL_HEAP_LOW 0x00000000
#define XE_MEMORY_PHYSICAL_HEAP_LOW 0x00010000
#define XE_MEMORY_PHYSICAL_HEAP_HIGH 0x20000000
#define XE_MEMORY_VIRTUAL_HEAP_LOW 0x20000000
#define XE_MEMORY_VIRTUAL_HEAP_HIGH 0x40000000

2
src/xenia/kernel/modules/xboxkrnl/xboxkrnl_memory.cc
View File

@ -222,7 +222,7 @@ uint32_t xeMmAllocatePhysicalMemoryEx(
// Round up the region size and alignment to the next page.
uint32_t adjusted_size = XEROUNDUP(region_size, page_size);
uint32_t adjusted_alignment = XEROUNDUP(alignment, page_size);;
uint32_t adjusted_alignment = XEROUNDUP(alignment, page_size);
// Callers can pick an address to allocate with min_addr_range/max_addr_range
// and the memory must be allocated there. I haven't seen a game do this,