From 4755f51dd12e4968d960964d79a0cd79e6f32852 Mon Sep 17 00:00:00 2001
From: "iliya.saroukha" <iliya.saroukhanian@etu.hesge.ch>
Date: Tue, 21 Jan 2025 17:46:53 +0100
Subject: [PATCH] feat: added notice about CR4.VMXE bit
---
docs/re.md | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/docs/re.md b/docs/re.md
index 73ffeaa..09e54e7 100644
--- a/docs/re.md
+++ b/docs/re.md
@@ -95,6 +95,11 @@ static bool vmx_supported(void) {
### Enabling VMX in CR4
+> [!IMPORTANT]
+> Looks like, when virtualization has been activated through the BIOS, the 13th
+> bit of CR4 is **always** set. Thus, setting this bit manually seems to be a
+> no-op.
+
In order to enter VMX operation, the software (our hypervisor) has to firstly
enable VMX by setting the 13th bit of the CR4 register to 1. This will of course
throw an exception if this code is being executed from user-space. That's why
--
GitLab