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

  - too many false positives due to memory that is mapped in
    legitimately (acpi, i/o devices)

diff --git a/servers/vm/alloc.c b/servers/vm/alloc.c
index a040750130d9eaf035e4d30c0f6d8b70f19ed68f..d112eb9f56fd30947708b585edbea211b35ee626 100644 (file)
--- a/servers/vm/alloc.c
+++ b/servers/vm/alloc.c
@@ -48,9 +48,6 @@ addr_avl addravl;
 
 /* Used for sanity check. */
 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 *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(!(len % VM_PAGE_SIZE));
        assert(len > 0);
-       assert_range(addr, len);
 
        pagestart = addr / VM_PAGE_SIZE;
        pages = len / VM_PAGE_SIZE;