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

Move old exception posts to old_posts folder

Browse Source
This commit is contained in:
Philipp Oppermann
2017-03-25 16:39:33 +01:00
parent 839cf7fba4
commit 3e5eceb1b3
5 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

0
blog/content/post/10-better-exception-messages.md → blog/content/old-posts/better-exception-messages.md
View File

0
blog/content/post/09-catching-exceptions.md → blog/content/old-posts/catching-exceptions.md
View File

2
blog/content/post/11-returning-from-exceptions.md → blog/content/old-posts/returning-from-exceptions.md
View File

@@ -295,7 +295,7 @@ Unfortunately, Rust does not support such a calling convention. It was [proposed
[interrupt calling conventions]: https://github.com/rust-lang/rfcs/pull/1275
[Naked functions]: https://github.com/rust-lang/rfcs/blob/master/text/1201-naked-fns.md
[naked fn post]: {{% relref "10-better-exception-messages.md#naked-functions" %}}
[naked fn post]: {{% relref "better-exception-messages.md#naked-functions" %}}
### A naked wrapper function

4
blog/content/post/02-entering-longmode.md
View File

@@ -499,8 +499,8 @@ _Congratulations_! You have successfully wrestled through this CPU configuration
#### One Last Thing
Above, we reloaded the code segment register `cs` with the new GDT offset. However, the data segment registers `ss`, `ds`, `es`, `fs`, and `gs` still contain the data segment offsets of the old GDT. This isn't necessarily bad, since they're ignored by almost all instructions in 64-bit mode. However, there are a few instructions that expect a valid data segment descriptor _or the null descriptor_ in those registers. An example is the the [iretq] instruction that we'll need in the [_Returning from Exceptions_] post.
[iretq]: {{% relref "11-returning-from-exceptions.md#the-iretq-instruction" %}}
[_Returning from Exceptions_]: {{% relref "11-returning-from-exceptions.md" %}}
[iretq]: {{% relref "returning-from-exceptions.md#the-iretq-instruction" %}}
[_Returning from Exceptions_]: {{% relref "returning-from-exceptions.md" %}}
To avoid future problems, we reload all data segment registers with null:

2
blog/content/post/08-kernel-heap.md
View File

@@ -835,4 +835,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]: {{% relref "09-catching-exceptions.md" %}}
[next post]: {{% relref "09-handling-exceptions.md" %}}