<?xml version="1.0"?>
<!DOCTYPE flagsdescription SYSTEM "http://www.spec.org/dtd/cpuflags2.dtd">
<flagsdescription>

<filename>Fujitsu-Platform-Settings-V1.2-SKL-RevA.xml</filename>

<title>SPEC CPU2006 Flag Description - Platform settings
</title>

<firmware>
 <![CDATA[ 
 
 <dl>
  	 <dt><b>Enable CPU HWPM(HWPM Support):</b></dt>
  	 <dd>
  	 This BIOS switch allows 4 options: "Native Mode", "Disabled", "Out of Band Mode" 
  	 and "Native Mode with No legacy Support". The default is "Native Mode".
 	 </dd>
  	 <dd>
  	 With Hardware Power Management(HWPM) the processors provides a flexible interface 
  	 between Hardware and Platform for performance management and improving energy efficiency.
  	 </dd>
  	 <dd>
  	 In Native Mode the HWPM operates cooperatively with the OS via a software interface 
  	 to provide constraints and hints.
  	 </dd>
  	 <dd>
  	 When disabled, system does not use HWPM.
  	 </dd>
 	 
	 <dt><b>Utilization Profile:</b></dt> 
	 <dd>
	 This BIOS switch allows 2 options: "Even" and "Unbalanced". The default is "Even" 
	 and the best choice for all workloads utilizing the whole system. In cases where 
	 the utilization is highly concentrated on few resources of the system the 
	 performance of the application could be improved by setting to "Unbalanced".          
	 </dd>
	 <dd>                
	 Setting this option to "Unbalanced" may improve performance but also 
	 increase the power consumption of the system. Users should only select 
	 this option after performing application benchmarking to verify improved
	 performance in their environment.
	 </dd>

	 <dt><b>Energy Performance:</b></dt> 
	 <dd>
	 This BIOS switch allows 4 options: "Balanced performance", "Performance", 
	 "Balanced Energy" and "Energy Efficient". The default is "Balanced Performance" 
	 optimized to maximum power savings with minimal impact on performance. 
	 "Performance" disables all power management options with any impact on performance. 
	 "Balanced Energy" is optimized for power efficiency and "Energy Efficient" for 
	 power savings. The BIOS switch is only selectable if the BIOS switch 
	 "Power Technology" is set to "Custom".
	 </dd>
	 <dd>                
	 The two options "Balanced Performance" and "Balanced Energy" should always be the
	 first choice as both options optimize the efficiency of the system. In cases where
	 the performance is not sufficient or the power consumption is too high the two
	 options "Performance" or "Energy Efficient" could be an alternative.
	 </dd>  
	 	  
	 <dt><b>Uncore Frequency Override:</b></dt> 
	 <dd>
     This BIOS switch allows 3 options: "Disabled", "Maximum" and "Nominal". The default
     is "Disabled" optimized for energy efficiency. "Maximum" sets the uncore frequency 
     to the fixed maximum uncore frequency available. "Nominal" reduces the uncore frequency
     to the nominal value.        
	 </dd>
	 <dd>                
	 Setting this option to "Maximum" may improve performance but also 
	 increase the power consumption of the system. Users should only select 
	 this option after performing application benchmarking to verify improved
	 performance in their environment.
	 </dd>

	 <dt><b>CPU C1E Support</b></dt>
	 <dd>                
	 Enabling this option which is the default allows the processor to transmit to its 
	 minimum frequency when entering the power state C1. If the switch is disabled the 
	 CPU stays at its maximum frequency in C1. Because of the increase of power 
	 consumption users should only select	this option after performing application 
	 benchmarking to verify improved performance in their environment. 
	 </dd>
 
	 <dt><b>Link Frequency Select</b></dt>
	 <dd>                
	This switch allows the configuration of the Intel Ultra Path Interconnect (UPI)
	link speed.  Default is auto, which configures the optimal link speed automatically. 
	It can be set "9.6 GT/s", "10.4 GT/s" or "Auto".
	 </dd>

	<dt><b>Patrol Scrub</b></dt> 
	<dd>
	This BIOS option enables or disables the so-called memory scrubbing, which cyclically
	accesses the main memory of the system in the background regardless of the operating
	system in order to detect and correct memory errors in a preventive way. The time of
	this memory test cannot be influenced and can under certain circumstances result in
	losses in performance. The disabling of the Patrol Scrub option increases the
	probability of discovering memory errors in case of active accesses by the operating
	system. Until these errors are correctable, the ECC technology of the memory modules
	ensures that the system continues to run in a stable way. However, too many correctable
	memory errors increase the risk of discovering non-correctable errors, which then
	 result in a system standstill.
	</dd>

	<dt><b>Intel Hyper-Threading Technology</b></dt> 
	<dd>
	This BIOS option enables or disables additional hardware thread which shares same
        physical core. Generally "Enabled" is recommended but disabling it makes sense
        for the application which requires the shortest possible response times.
        Default setting is "Enabled".
	</dd>

	<dt><b>Intel Virtualization Technology</b></dt> 
	<dd>
	This BIOS option enables or disables additional virtualization functions of the CPU.
        If the server is not used for virtualization, this option should be set to "Disabled".
        This can result in energy savings.  Default setting is "Enabled".
	</dd>

	<dt><b>VT-d</b></dt> 
	<dd>
	This BIOS option enables or disables I/O virtualization functions of the CPU.
        If the server is not used for virtualization, this option should be set to "Disabled".
	Default setting is "Enabled".
	</dd>

	<dt><b>Sub NUMA Cluster</b></dt>
	<dd>
	Sub NUMA Cluster (SNC) breaks up the last-level cache (LLC) into two disjoint clusters
	based on address range, with each cluster bound to one memory controller.  SNC improves
	average latency to the LLC/memory and is a replacement for the "Cluster On Die" (COD)
	feature found in previous processor families.
	For a multi-socketed system, all SNC clusters are mapped to unique NUMA domains.
	IMC Interleaving must be set to the correct value to correspond with SNC enable/disable.
	If SNC and IMC Interleave are both set to Auto, the result will be SNC disabled (only one
	cluster per socket) with 2-way IMC interleave.  If SNC is set to Enable, IMC Interleave
	should be set to 1-way, which will result in two clusters per socket.
	The BIOS switch "Sub NUMA Clustering" allows 3 options: "auto", "enabled" and "disabled".
	The default setting is "enabled" (PRIMERGY servers), "auto" (PRIMEQUEST servers).
	</dd>

	<dt><b>IMC Interleaving</b></dt>
	<dd>
	This BIOS option controls the interleaving between the Integrated Memory Controllers (IMCs).
	There are two IMCs per socket in Skylake Server.  If IMC Interleaving is set to 2-way,
	addresses will be interleaved between the two IMCs.  If IMC Interleaving is set to 1-way,
	there will be no interleaving.  If SNC is disabled, IMC Interleaving should be set to 2-way.
	If SNC is enabled, IMC Interleaving should be set to 1-way.
	Default setting is "Auto".
	</dd>

	<dt><b>LLC Dead Line Alloc</b></dt>
	<dd>
	This BIOS switch allows 2 options: "Enabled" and "Disabled". The default is "Enabled".
	In the Skylake non-inclusive cache scheme, the mid-level cache (MLC) evictions are filled
	into the last-level cache (LLC).  When lines are evicted from the MLC, the core can flag them
	as "dead" (i.e., not likely to be read again).
	The LLC has the option to drop dead lines and not fill them in the LLC.
	If the Dead Line LLC Alloc feature is disabled, dead lines will always be dropped and will
	never fill into the LLC. This can help save space in the LLC and prevent the LLC from evicting
	useful data. However, if the Dead Line LLC Alloc feature is enabled, the LLC can
	opportunistically fill dead lines into the LLC if there is free space available.
	</dd>

	<dt><b>Stale AtoS (Directory AtoS)</b></dt>
	<dd>
	This BIOS switch allows 2 options: "Enabled" and "Disabled". The default is "Disabled".
	</dd>
	<dd>
	The in-memory directory has three states: I, A, and S.
	I (invalid) state means the data is clean and does not exist in any other socket's cache.
	A (snoopAll) state means the data may exist in another socket in exclusive or modified state.
	S (Shared) state means the data is clean and may be shared across one or more socket's caches.
	</dd>
	<dd>
	When doing a read to memory, if the directory line is in the A state we must snoop all the
	other sockets because another socket may have the line in modified state. If this is the case,
	the snoop will return the modified data. However, it may be the case that a line is read in
	A state and all the snoops come back a miss. This can happen if another socket read the line
	earlier and then silently dropped it from its cache without modifying it.
	</dd>
	<dd>
	If Stale AtoS feature is enabled, in the situation where a line in A state returns only snoop
	misses, the line will transition to S state. That way, subsequent reads to the line will
	encounter it in S state and not have to snoop, saving latency and snoop bandwidth.
	Stale AtoS may be beneficial in a workload where there are many cross-socket reads.
	</dd>

	<dt><b>nohz_full</b></dt> 
	<dd>
	This kernel option sets adaptive tick mode (NOHZ_FULL) to specified processors.
	Since the number of interrupts is reduced to ones per second, latency-sensitive
	applications can take advantage of it.
	</dd>

	<dt><b>isolcpus</b></dt> 
	<dd>
	This kernel option excludes a specified processor from load balancing by the kernel
	scheduler.  This prevents the scheduler from scheduling any user-space threads on
	this processor. 
	</dd>

	<dt><b>sched_min_granularity_ns</b></dt> 
	<dd>
	This OS setting controls the minimal preemption granularity for CPU bound tasks.
	As the number of runnable tasks increases, CFS(Complete Fair Scheduler), the scheduler
	of the Linux kernel, decreases the timeslices of tasks. If the number of runnable
	tasks exceeds sched_latency_ns/sched_min_granularity_ns, the timeslice becomes
	number_of_running_tasks * sched_min_granularity_ns.  The default value is 4000000 (ns). 
	</dd>

	<dt><b>sched_wakeup_granularity_ns</b></dt> 
	<dd>
	This OS setting controls the wake-up preemption granularity. Increasing this variable
	reduces wake-up preemption, reducing disturbance of compute bound tasks.
	Lowering it improves wake-up latency and throughput for latency critical tasks,
	particularly when a short duty cycle load component must compete with CPU bound components. 
	The default value is 2500000 (ns). 
	</dd>

	<dt><b>numa_balancing</b></dt> 
	<dd>
	This OS setting controls automatic NUMA balancing on memory mapping and process placement.
	Setting 0 disables this feature.  It is enabled by default (1).
	</dd>

	<dt><b>cpupower frequency-set</b></dt>
	<dd>
	cpupower utility is a collection of tools for power efficiency of processor.
	frequency-set sub-command controls settings for processor frequency.
	"-g [governor]" specifies a policy to select processor frequency.
	The performance governor statically sets frequency of the processor cores specified
	by "-c" option to the highest possible for maximum performance.
	</dd>

	<dt><b>cpupower idle-set</b></dt>
	<dd>
	idle-set sub-command of cpupower utility controls a processor idle state (C-state) of
	the kernel.  "-d [state_no]>" option disables a specific processor idle state.
	Disabling idle state can reduce the idle-wakeup delay, but it results in substantially
	higher power consumption.  By default, processor idle states of all CPU cores are set.
	</dd>

 </dl>	


  ]]> 
</firmware>

</flagsdescription>
