From 64ec8aa157e5d5d09372def37cbab00628e1e5f5 Mon Sep 17 00:00:00 2001
From: Marvin Borner
Date: Tue, 6 Apr 2021 22:20:58 +0200
Subject: Made exec syscall relative using app name

My plan is to implement a mobile-OS-like sandboxing using manifests
and permission middlewares. Let's see if I can manage to do this
without sacrificing too much performance.

I'm also wondering whether I should implement open/close syscalls
which would result in a cleaner block/unblock mechanism. I need to
think. Hmmm.. Naa
---
 kernel/drivers/cpu.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'kernel/drivers')

diff --git a/kernel/drivers/cpu.c b/kernel/drivers/cpu.c
index 86ae2be..f751d33 100644
--- a/kernel/drivers/cpu.c
+++ b/kernel/drivers/cpu.c
@@ -145,7 +145,7 @@ CLEAR void cpu_enable_features(void)
 		panic("No FPU support!\n");
 	}
 
-	// Enable NX (IA32_EFER.NXE)
+	// Enable NX (IA32_EFER.NXE) // TODO: Use NX Bit? (only possible in PAE 64 bit paging?)
 	if (cpu_extended_information.edx & CPUID_EXT_INFO_EDX_NX) {
 		__asm__ volatile("movl $0xc0000080, %ecx\n"
 				 "rdmsr\n"
-- 
cgit v1.2.3