From f737c302e7f7bc7e917112fbf902dfbfe25c73ce Mon Sep 17 00:00:00 2001 From: Philipp Oppermann Date: Mon, 31 Oct 2016 15:21:32 +0100 Subject: [PATCH] therefor -> for that --- blog/post/07-remap-the-kernel.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/post/07-remap-the-kernel.md b/blog/post/07-remap-the-kernel.md index 76cbe378..ee310ad6 100644 --- a/blog/post/07-remap-the-kernel.md +++ b/blog/post/07-remap-the-kernel.md @@ -969,7 +969,7 @@ This time the responsible function is `controlregs::cr3_write()` itself. From th The reason is that the `NO_EXECUTE` bit must only be used when the `NXE` bit in the [Extended Feature Enable Register] \(EFER) is set. That register is similar to Rust's feature gating and can be used to enable all sorts of advanced CPU features. Since the `NXE` bit is off by default, we caused a page fault when we added the `NO_EXECUTE` bit to the page table. [Extended Feature Enable Register]: https://en.wikipedia.org/wiki/Control_register#EFER -So we need to enable the `NXE` bit. Therefor we use Gerd Zellweger's awesome [x86][rust-x86] crate again: +So we need to enable the `NXE` bit. For that we use the awesome [x86][rust-x86] crate again: [rust-x86]: https://github.com/gz/rust-x86 ```rust