michaelkuc6/blog_os
1
0
Fork 0
mirror of https://github.com/phil-opp/blog_os.git synced 2025-12-17 06:47:49 +00:00
Code Issues Projects Releases Wiki Activity

Update to new internal link syntax

Browse Source
This commit is contained in:
Philipp Oppermann
2019-09-29 15:24:21 +02:00
parent 0b971c9128
commit a133ea82cf
29 changed files with 117 additions and 119 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
blog/content/first-edition/posts/08-kernel-heap/index.md
View File

@@ -10,8 +10,8 @@ template = "first-edition/page.html"
In the previous posts we created a [frame allocator] and a [page table module]. Now we are ready to create a kernel heap and a memory allocator. Thus, we will unlock `Box`, `Vec`, `BTreeMap`, and the rest of the [alloc] crate.
[frame allocator]: ./first-edition/posts/05-allocating-frames/index.md
[page table module]: ./first-edition/posts/06-page-tables/index.md
[frame allocator]: @/first-edition/posts/05-allocating-frames/index.md
[page table module]: @/first-edition/posts/06-page-tables/index.md
[alloc]: https://doc.rust-lang.org/nightly/alloc/index.html
<!-- more -->
@@ -460,8 +460,8 @@ That's it. Now our `memory::init` function can only be called once. The macro wo
### Mapping the Heap
Now we're ready to map the heap pages. In order to do it, we need access to the `ActivePageTable` or `Mapper` instance (see the [page table] and [kernel remapping] posts). For that we return it from the `paging::remap_the_kernel` function:
[page table]: ./first-edition/posts/06-page-tables/index.md
[kernel remapping]: ./first-edition/posts/07-remap-the-kernel/index.md
[page table]: @/first-edition/posts/06-page-tables/index.md
[kernel remapping]: @/first-edition/posts/07-remap-the-kernel/index.md
```rust
// in src/memory/paging/mod.rs
@@ -736,4 +736,4 @@ Now we're able to use heap storage in our kernel without leaking memory. This al
## What's next?
This post concludes the section about memory management for now. We will revisit this topic eventually, but now it's time to explore other topics. The upcoming posts will be about CPU exceptions and interrupts. We will catch all page, double, and triple faults and create a driver to read keyboard input. The [next post] starts by setting up a so-called _Interrupt Descriptor Table_.
[next post]: ./first-edition/posts/09-handling-exceptions/index.md
[next post]: @/first-edition/posts/09-handling-exceptions/index.md