From: Peter Dinda <pdinda@northwestern.edu>
Date: Tue, 26 Nov 2013 01:52:14 +0000 (-0600)
Subject: Updated defaults to reflect former behavior for CPUID, MSRs, FP-Switching
X-Git-Url: http://v3vee.org/palacios/gitweb/gitweb.cgi?p=palacios.git;a=commitdiff_plain;h=74c8b93121e177a843f461c8e0538ae1691ebcc8

Updated defaults to reflect former behavior for CPUID, MSRs, FP-Switching

The user must explicitly enable custom cpuid, strict msrs, and fp-swithing
---

diff --git a/Kconfig b/Kconfig
index 028645f..63d9eb7 100644
--- a/Kconfig
+++ b/Kconfig
@@ -150,7 +150,7 @@ menu "Virtual core specialization"
 
 config CUSTOM_CPUID
 	bool "Use custom CPU information (vendor, etc)"
-	default y
+	default n
 	help 
           If set, the CPU information will be for a special V3VEE vendor.
 	  This should result in identical guest kernel setup, regardless
@@ -159,14 +159,14 @@ config CUSTOM_CPUID
 
 config STRICT_MSR_SEMANTICS
 	bool "Use strict RDMSR/WRMSR semantics"
-	default y
+	default n
 	help
 	  Use strict MSR semantics - when an unhandled MSR is read or written,
 	  a GPF is generated.  This is typically usd with CUSTOM_CPU_TYPE on.
 
 config FP_SWITCH
 	bool "Floating point context switching"
-        default y
+        default n
         help
           If set, floating point is handled for context switches 
           (VM1->VM2->VM1 and/or VM->HOST->VM).   This can be disabled