From ca07527ede16381122470890d5a76f2716461f38 Mon Sep 17 00:00:00 2001 From: Philipp Oppermann Date: Sun, 15 Nov 2015 02:09:20 +0100 Subject: [PATCH] Add `What's next?` text --- posts/DRAFT-allocating-frames.md | 13 +------------ 1 file changed, 1 insertion(+), 12 deletions(-) diff --git a/posts/DRAFT-allocating-frames.md b/posts/DRAFT-allocating-frames.md index 824afae7..6c3dda6c 100644 --- a/posts/DRAFT-allocating-frames.md +++ b/posts/DRAFT-allocating-frames.md @@ -346,18 +346,7 @@ You can try different amounts of memory by passing e.g. `-m 500M` to QEMU. To co [WolframAlpha]: http://www.wolframalpha.com/input/?i=%2832698+*+4096%29+bytes+in+MiB ## What's next? - -### Remapping the Kernel Sections -We can use the ELF section tag to write a skeleton that remaps the kernel correctly: - -```rust -for section in multiboot.elf_tag().sections() { - for page in start_page..end_page { - // TODO identity_map(page, section.writable(), section.executable()) - } -} -``` -TODO +The next post will be about paging again. But this time we will use the frame allocator to create a safe rust module that allows us to switch page tables and map pages. Then we will use this module and the information from the ELF sections tag to remap the kernel correctly. ## Recommended Posts Eric Kidd started the [Bare Metal Rust] series last week. Like this post, it builds upon the code from [Printing to Screen], but tries to support keyboard input instead of wrestling through memory management details ;).