oneechanhax/phunix
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

vm: don't check the range of memory during sanity checking

Browse Source 
- too many false positives due to memory that is mapped in
    legitimately (acpi, i/o devices)
This commit is contained in:
Ben Gras 2010-10-04 11:38:33 +00:00
parent 677d80b781
commit 36189370a5
1 changed files with 0 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
servers/vm/alloc.c
View File

@ -48,9 +48,6 @@ addr_avl addravl;
/* Used for sanity check. */ /* Used for sanity check. */
PRIVATE phys_bytes mem_low, mem_high; PRIVATE phys_bytes mem_low, mem_high;
#define assert_range(addr, len) \
assert((addr) >= mem_low); \
assert((addr) + (len) - 1 <= mem_high);
struct hole { struct hole {
struct hole *h_next; /* pointer to next entry on the list */ struct hole *h_next; /* pointer to next entry on the list */
@ -841,7 +838,6 @@ int usedpages_add_f(phys_bytes addr, phys_bytes len, char *file, int line)
assert(!(addr % VM_PAGE_SIZE)); assert(!(addr % VM_PAGE_SIZE));
assert(!(len % VM_PAGE_SIZE)); assert(!(len % VM_PAGE_SIZE));
assert(len > 0); assert(len > 0);
assert_range(addr, len);
pagestart = addr / VM_PAGE_SIZE; pagestart = addr / VM_PAGE_SIZE;
pages = len / VM_PAGE_SIZE; pages = len / VM_PAGE_SIZE;