Another `last boundary' test taking a different code path. This time

the allocation triggers a `boundary fixup' but should nevertheless
fit in the remaining space of the map.
This commit is contained in:
pk 2000-06-27 21:30:03 +00:00
parent d28770775b
commit 0c19f5a36f
2 changed files with 18 additions and 2 deletions

View File

@ -1,4 +1,4 @@
# $NetBSD: extest.exp,v 1.3 2000/06/27 21:08:30 pk Exp $
# $NetBSD: extest.exp,v 1.4 2000/06/27 21:30:03 pk Exp $
# real output must start in line 4
output for test1
@ -31,3 +31,9 @@ result: 0x8
result: 0xa
extent `test6' (0x0 - 0xc), flags = 0x0
0x0 - 0xb
output for test7
result: 0x0
result: 0x8
extent `test7' (0x0 - 0xc), flags = 0x0
0x0 - 0x6
0x8 - 0xb

View File

@ -1,4 +1,4 @@
# $NetBSD: tests,v 1.3 2000/06/27 21:08:31 pk Exp $
# $NetBSD: tests,v 1.4 2000/06/27 21:30:03 pk Exp $
#fill up an extent, should coalesce into one allocation
extent test1 0 0x4f
@ -36,9 +36,19 @@ alloc_subregion 0xf0000000 0xffffffff 0x1
print
#check allocation beyond last boundary line (to be fixed)
# last two allocations should succeed without boundary "fixups"
extent test6 0 12
boundary 8
alloc_subregion 0 12 8
alloc_subregion 0 12 2
alloc_subregion 0 12 2
print
#check allocation beyond last boundary line (to be fixed)
# last allocation should be bumped to the next boundary and exactly fit
# the remaining space
extent test7 0 12
boundary 8
alloc_subregion 0 12 7
alloc_subregion 0 12 4
print