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

<flagsdescription>

<!--
######################################################################################################
       This platform flags file is supplied as an example. Please document bios/firmware settings in your
       systems that are set to non-default values for performance runs.  

       You MUST change the filename tag just below; at the very least, change "Invalid" to your company name.
######################################################################################################
-->

<filename>Bull-BullionS-Flags-V2.2</filename>

<title>SPEC CPU2006 Platform Settings for Intel-based systems</title>

<firmware>

<![CDATA[
<dl>
<dt><b>Efficiency Policy</b></dt> 
<dd>
         <p>This BIOS option allows you to determine whether system Performance or energy efficiency is more important on server. This can be one of the following:
         Balanced Energy, Balanced Performance, Energy Efficient and Performance.
</p></dd>
<dt><b>Memory RAS mode</b></dt> 
<dd>
      <p>This BIOS option allows to configure memory reliability, availability and serviceability (RAS).
       Setting this BIOS option to Performance, system performance is optimized
       Setting this BIOS option to RAS mode, lockstep technology is enabled and serviceability is improved.
</p></dd>
<dt><b>Patrol Scrub</b></dt> 
<dd>
      <p>This BIOS option allows to configure the periodicity of memory scrubbing.
       Setting this BIOS option to Disable, no systematic periodic scrubbing is done
       Setting this BIOS option to an integer from 1 to 24 ensures all the memory is scanned in that number of hours
</p></dd>

<dt><b>Intel Turbo boost Technology</b></dt> 
   <dd>
   <p>Enabling this option allows the processor cores to automatically increase its frequency and increasing 
       performance if it is running below power, temperature.
       </p>
       </dd>       
<dt><b>ulimit -s &lt;n&gt; </b></dt>
   <dd>
        <p>Sets the stack size to <b>n</b> kbytes, or <b>unlimited</b> to allow the stack size 
         to grow without limit.
         </p>
         </dd>    

<dt><b>numactl --interleave=all "runspec command"</b></dt> 
   <dd>
   <p>Launching a process with numactl --interleave=all sets the memory interleave policy so that memory will be allocated using 
   round robin on nodes. When memory cannot be allocated on the current interleave target fall back to other nodes. 
   </p>
   </dd>
<dt><b>Force Full Fan Speed</b></dt>
<dd>
<p>The Baseboard Management Controller allows the consfiguration of functional profiles.
The default functional profile is modified to set the Full Fan Speed option.
</p>
</dd>

<dt><b>Mount options to tmpfs interleave mode</b></dt>
<dd>
<p>
mpol=[default|prefer:Node|bind:NodeList|interleave|interleave:NodeList]
Set the NUMA memory allocation policy for all files in that instance (if the kernel CONFIG_NUMA is enabled) - which can be adjusted on the fly via 'mount -o remount ...'</p>
<p>default</p>
<p>prefers to allocate memory from the local node</p>
<p>prefer:Node</p>
<p>prefers to allocate memory from the given Node</p>
<p>bind:NodeList</p>
<p>allocates memory only from nodes in NodeList</p>
<p>interleave</p>
<p>prefers to allocate from each node in turn</p>
<p>interleave:NodeList</p>
<p>allocates from each node of NodeList in turn.</p>
<p>
The NodeList format is a comma-separated list of decimal numbers and ranges, a range being two hyphen-separated decimal numbers, the smallest and largest node numbers in the range. For example, mpol=bind:0-3,5,7,9-15
Note that trying to mount a tmpfs with an mpol option will fail if the running kernel does not support NUMA; and will fail if its nodelist specifies a node which is not online. If your system relies on that tmpfs being mounted, but from time to time runs a kernel built without NUMA capability (perhaps a safe recovery kernel), or with fewer nodes online, then it is advisable to omit the mpol option from automatic mount options. It can be added later, when the tmpfs is already mounted on MountPoint, by 'mount -o remount,mpol=Policy:NodeList MountPoint'.
</p>

<p> The directory containing all spec files, including temporary and binary files, is mapped to memory.
This directory is created using linux command <code>mount -t tmpfs -o size=1536g,rw,mpol=interleave none /specRam</code>
then all spec files are copied into it before starting the test.
One TB is allocated evenly distributed on all the numa nodes.
</p>
</dd>
</dl>
]]>
</firmware>


</flagsdescription>