X-Git-Url: http://v3vee.org/palacios/gitweb/gitweb.cgi?a=blobdiff_plain;f=Kconfig;h=028645fb3a22bd75b214d4b0efa72b9df0d6a5e2;hb=4289236a2f36c2556c4c333d13790e4325cbcb85;hp=71b85eb31cf9c68a81bd0fdc3f2f6110eebaa553;hpb=179cda8c3c2686bb4605f67ec6d525d2951c618f;p=palacios.releases.git

diff --git a/Kconfig b/Kconfig
index 71b85eb..028645f 100644
--- a/Kconfig
+++ b/Kconfig
@@ -75,6 +75,7 @@ config VMX
 	  Compile with support for Intel VMX
 
 
+
 config FRAME_POINTER
 	bool "Compile with Frame pointers"
 	default n
@@ -116,7 +117,15 @@ config QUIX86_DEBUG
 endchoice
 
 menu "Supported host OS features"
-      
+
+config MEM_BLOCK_SIZE
+        int "Allocation size for underlying VM memory"
+        default 134217728
+        help 
+          This is the default size in bytes of the underlying memory allocations used for the base memory regions.
+          A good default value is 128MB (134217728 or 0x8000000 bytes).  Note that the host interface must be able
+          to provide contiguous memory of at least this size in order for VMs to typically work.   This 
+          value can be overriden via a load-time option, provided the host supports this.
 
 config ALIGNED_PG_ALLOC
 	bool "Host support for aligned page allocations"
@@ -136,6 +145,49 @@ config MAX_CPUS
 endmenu
 
 source "palacios/src/interfaces/Kconfig"
+
+menu "Virtual core specialization"
+
+config CUSTOM_CPUID
+	bool "Use custom CPU information (vendor, etc)"
+	default y
+	help 
+          If set, the CPU information will be for a special V3VEE vendor.
+	  This should result in identical guest kernel setup, regardless
+          of the underlying hardware, but it also means that the guest kernel
+          has no chance of employing CPU-specific bug fixes.
+
+config STRICT_MSR_SEMANTICS
+	bool "Use strict RDMSR/WRMSR semantics"
+	default y
+	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
+        help
+          If set, floating point is handled for context switches 
+          (VM1->VM2->VM1 and/or VM->HOST->VM).   This can be disabled
+          for environments where a single VM is the only user of FP.
+          Note that even if disabled, FP save/restore code is included
+          for support of checkpoint/restore.
+
+config LAZY_FP_SWITCH
+	bool "Use host-based lazy floating point context switching"
+        depends on FP_SWITCH && HOST_LAZY_FPU_SWITCH
+	default y
+	help
+	  When true,  the host's lazy floating point save/restore 
+          mechanism is notified on each exit and entry.  If false,
+          the floating point state is explicitly saved on each exit
+          and restored on each entry---this save/restore is entirely
+          done in Palacios.
+          
+          
+endmenu
+
 source "palacios/src/extensions/Kconfig"
 
 config TELEMETRY