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

<!-- =====================================================================
  Information about the meaning of boot-time settings, BIOS options,
  kernel tuning, and so forth go in this separate 'platform_settings' file.

  They'll be appended to the end of both the flags dump and per-result flag report.

  As the contents should be HTML, it will save lots of time to just enclose
  the whole thing in a CDATA section.  Section 2.3.1 again.

  NOTE that these should be vendor, or platform, specific and thus the file
  should be named in a way to identify which platform was used.  For example,
  one could replace the string Example with the vendor name in the filename,
  i.e. ACME-linux-platform-revA.xml.
     ===================================================================-->

<!-- This file defines platform settings -->
<flagsdescription>

<filename>GIGA-BYTE-Platform-SPECcpu2017-Flags-V1.0-Intel-Purley.xml</filename>

<title>SPEC CPU2017 Platform Settings for GIGA-BYTE Intel Purley platform</title>

<!-- Platform Settings -->
<submit_command>

</submit_command>

<firmware>
<![CDATA[
<dl>

  <dt><b>Power Policy Quick Settings</b></dt>
  <dd>
         <p>This BIOS option controls the performance or power save setting, user can use this item to change it. Best performance can maximize the performance of the server. Energy efficiency can maximize the power efficiency of the server.</p>
         <p>Values for this BIOS setting can be:</p>
         <p>Standard: BIOS default setting.</p>
		 <p>Best Performance: Maximize the performance of the server.</p>
         <p>Energy Efficiency: Maximize the power efficiency of the server.</p>
  </dd>

  <dt><b>SNC(Sub-NUMA Clustering)</b></dt>
  <dd>
  	<p>SNC breaks up the last level cache (LLC) into disjoint clusters based on address range, with each cluster bound to a subset of the memory controllers in the system. SNC improves average latency to the LLC and memory. 
       SNC 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 (Non Uniform Memory Access) domains. </p>
    <p>SNC AUTO supports 1-cluster or 2-clusters depending on IMC interleave. SNC and IMC interleave both AUTO will support 1-cluster 2-way IMC interleave.</p>
    <p>SNC Enable supports Full SNC (2 clusters) and 1-way IMC interleave.</p>
    <p>SNC disable supports 1-cluster and 2-way IMC interleave, the LLC is treated as one cluster.</p>
  </dd>
  
  <dt><b>Stale AtoS (Directory AtoS)</b></dt>
  <dd>
	<p>This BIOS switch allows 2 options: "Enabled" and "Disabled". The default is "Disabled".</p>
	</dd>
	<dd>
	<p>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.</p>
	</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>
	<p>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.</p>
	</dd>  
  <dt><b>LLC dead line alloc</b></dt>
	   <dd>
	    <p>In some Intel CPU caching schemes, mid-level cache (MLC) evictions are filled into the last level cache (LLC). If a line is evicted from the MLC to the LLC, the core can flag the evicted MLC lines as "dead.” 
		   This means that the lines are not likely to be read again. This option allows dead lines to be dropped and never fill the LLC if the option is disabled.</p>
	    <p>Values for this BIOS option can be: </p>		
		<p>Disabled: Disabling this option can save space in the LLC by never filling MLC dead lines into the LLC.</p>
		<p>Enabled: Opportunistically fill MLC dead lines in LLC, if space is available.</p>
	  </dd> 

  <dt><b>IMC Interleaving</b></dt>
	<dd>
	<p>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".</p>
	</dd>
  
  <dt><b>Patrol Scrub</b></dt>
	<dd>
	<p>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.</p>
	</dd>
  
</dl>

]]>
</firmware>

</flagsdescription>
