Skip to contentSkip to conversation

relax free_area() for compatibility with free_bootmem()

PATCH New Jan Beulich 1 participant 1 message Mar 26, 2010

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 relax free_area() for compatibility with free_bootmem()

To be compatible with the traditional free_bootmem() (which is just a wrapper around free_earl() under CONFIG_NO_BOOTMEM), free_area() should allow freeing not only exact ranges, but also proper subsets. This is still different from free_early_partial() in that the latter also handles an input range spanning multiple reserved ranges, possibly even with holes between them (not that I think permitting this is a good idea).

---
 kernel/early_res.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
kernel/early_res.c +2 -2
@@ -321,11 +321,11 @@ void __init free_early(u64 start, u64 en
 
 	i = find_overlapped_early(start, end);
 	r = &early_res[i];
-	if (i >= max_early_res || r->end != end || r->start != start)
+	if (i >= max_early_res || r->end < end || r->start > start)
 		panic("free_early on not reserved area: %llx-%llx!",
 			 start, end - 1);
 
-	drop_range(i);
+	drop_range_partial(i, start, end);
 }
 
 void __init free_early_partial(u64 start, u64 end)