From 842d2aa5f9f6a36daefc19ef18396b2d9f565fd9 Mon Sep 17 00:00:00 2001
From: Sir Richard <sir_richard@svn.reactos.org>
Date: Tue, 26 Jan 2010 19:39:21 +0000
Subject: [PATCH] [PERF]: What to do when your SYSEXIT code has a bug? Set
 KiFastSystemCallDisable to TRUE so it never gets used. Now, for the first
 time in 3 years and 3 months (not giving a specific revision # to protect the
 'innocent'), ReactOS actually fully uses the SYSENTER/SYSEXIT instructions
 isntead of IRETD, since my code doesn't exhibit the bug and SYSEXIT is safe
 to use. This should save a good hundred cycles or more per system call.

svn path=/trunk/; revision=45271
---
 reactos/ntoskrnl/ke/i386/cpu.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/reactos/ntoskrnl/ke/i386/cpu.c b/reactos/ntoskrnl/ke/i386/cpu.c
index 4aadb0f3317..6cf6e8676b8 100644
--- a/reactos/ntoskrnl/ke/i386/cpu.c
+++ b/reactos/ntoskrnl/ke/i386/cpu.c
@@ -27,7 +27,7 @@ ULONG KeProcessorArchitecture;
 ULONG KeProcessorLevel;
 ULONG KeProcessorRevision;
 ULONG KeFeatureBits;
-ULONG KiFastSystemCallDisable = 1;
+ULONG KiFastSystemCallDisable;
 ULONG KeI386NpxPresent = 0;
 ULONG KiMXCsrMask = 0;
 ULONG MxcsrFeatureMask = 0;