vmbase: Map .bss, .data, & stack separately
Map the "scratch" (.data & .bss) and stack regions separately to allow
them to be placed in non-contiguous regions.
Note: No functional change intended.
Test: atest vmbase_example.integration_test
Test: atest rialto_test
Test: atest MicrodroidTests
Change-Id: I6c3f8e4957e39e1c966a219149b253360782ba8e
diff --git a/vmbase/src/layout.rs b/vmbase/src/layout.rs
index b5ab449..0d824bb 100644
--- a/vmbase/src/layout.rs
+++ b/vmbase/src/layout.rs
@@ -66,9 +66,9 @@
linker_region!(boot_stack_begin, boot_stack_end)
}
-/// Writable data, including the stack.
-pub fn writable_region() -> Range<usize> {
- linker_region!(data_begin, boot_stack_end)
+/// All writable sections, excluding the stack.
+pub fn scratch_range() -> Range<usize> {
+ linker_region!(data_begin, bss_end)
}
/// Read-write data (original).