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

Update mentions of bootimage run in other posts

Browse Source
This commit is contained in:
Philipp Oppermann
2019-04-25 15:06:29 +02:00
parent 52cbb1e756
commit 82c499a8b9
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
blog/content/second-edition/posts/06-cpu-exceptions/index.md
View File

@@ -392,7 +392,7 @@ pub extern "C" fn _start() -> ! {
}
```
When we run it in QEMU now (using `bootimage run`), we see the following:
When we run it in QEMU now (using `cargo xrun`), we see the following:
![QEMU printing `EXCEPTION: BREAKPOINT` and the interrupt stack frame](qemu-breakpoint-exception.png)

6
blog/content/second-edition/posts/08-hardware-interrupts/index.md
View File

@@ -134,7 +134,7 @@ We use the [`initialize`] function to perform the PIC initialization. Like the `
[`initialize`]: https://docs.rs/pic8259_simple/0.1.1/pic8259_simple/struct.ChainedPics.html#method.initialize
If all goes well we should continue to see the "It did not crash" message when executing `bootimage run`.
If all goes well we should continue to see the "It did not crash" message when executing `cargo xrun`.
## Enabling Interrupts
@@ -160,7 +160,7 @@ pub extern "C" fn _start() -> ! {
}
```
The `interrupts::enable` function of the `x86_64` crate executes the special `sti` instruction (“set interrupts”) to enable external interrupts. When we try `bootimage run` now, we see that a double fault occurs:
The `interrupts::enable` function of the `x86_64` crate executes the special `sti` instruction (“set interrupts”) to enable external interrupts. When we try `cargo xrun` now, we see that a double fault occurs:
![QEMU printing `EXCEPTION: DOUBLE FAULT` because of hardware timer](qemu-hardware-timer-double-fault.png)
@@ -256,7 +256,7 @@ The `notify_end_of_interrupt` figures out whether the primary or secondary PIC s
We need to be careful to use the correct interrupt vector number, otherwise we could accidentally delete an important unsent interrupt or cause our system to hang. This is the reason that the function is unsafe.
When we now execute `bootimage run` we see dots periodically appearing on the screen:
When we now execute `cargo xrun` we see dots periodically appearing on the screen:
![QEMU printing consequtive dots showing the hardware timer](qemu-hardware-timer-dots.gif)