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

<!--
-->
<!-- The lines above are NOT optional.  If you're adept at reading DTDs,
     the one that this file conforms to is at the URL listed above.  
     
     But most humans writing a flags file will want to have it automatically 
     checked using a validating parser such as RXP (available at
     http://www.ltg.ed.ac.uk/~richard/rxp.html), or use one of the on-line
     parsers:
       http://www.stg.brown.edu/service/xmlvalid/
       http://www.cogsci.ed.ac.uk/~richard/xml-check.html
     
     The parser used by the CPU tools is _not_ a validating parser, so it
     may be possible to sneak things by it that would not pass the checkers
     above.  However, if the checkers above say that your file is clean, it's
     clean.

     Flag files submitted to SPEC _will_ be checked by a validating parser.
     Invalid or not-well-formed flag files will be rejected.
-->

<!-- **********************************************************************
     **********************************************************************
     Unless otherwise explicitly noted, all references to "section n.nn"
     refer to flag_description.html, available at

     http://www.spec.org/cpu2006/docs/flag_description.html
     **********************************************************************
     ********************************************************************** -->

<!--
     This file is
       Copyright (C) 2006 Standard Performance Evaluation Corporation
       All Rights Reserved
     
     This file may be freely modified and redistributed, provided that the
     copyright notice above and this notice remain unaltered.

-->

<flagsdescription>

<filename>vesnin_platform-V1.3.xml</filename>

<title>Yadro Vesnin Flags file</title>

<style>
<![CDATA[
body { background: white; }
]]>
</style>

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

  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.
     ===================================================================-->

<sw_environment>
<![CDATA[

<ul>
<li>Environment variables that can be set before the run:
<pre>
XLFRTEOPTS=intrinthrds=1 : Causes the Fortran runtime to only use a single thread.
</pre></li>


<li> To reserve 16000 huge pages out of the physical memory pool, issue the following command,
<pre>
echo 16000 > /proc/sys/vm/nr_hugepages
</pre> 
or 
<pre>
echo 16000 > /proc/sys/vm/nr_overcommit_hugepages
</pre>
to allocate from the dynamic hugepage pool.

This can be done in both Red Hat and Suse Enterprise, since both distributions implements Transparent Huge Pages (THP).
THP is an abstraction layer that automates most aspects of creating, managing and using huge pages, and can currently only map anonymous memory regions such as heap and stack space. 
</li>
</ul>

]]>
</sw_environment>

<os_tuning>
<![CDATA[

<ul>
<li> <kbd>ulimit -s unlimited</kbd> 
<br />Sets the maximum stack size to "<kbd>unlimited</kbd>".</li>
</ul>

]]>
</os_tuning>

<firmware>
<![CDATA[

<ul>
<li>Intelligent Energy Optimizations</li>
</ul>
<pre>
Intelligent Energy Optimization capabilities enable the POWER8 processor to operate at a higher frequency for increased performance. This processor / firmware feature maximizes performance as thermal conditions allow and enabled by default in firmware.

</pre>

<ul>

<li>Spectre and Meltdown vulnerabilities mitigation status</li>
</ul>
<pre>
   1. The test sponsor attests that CVE-2017-5754 (Meltdown) is mitigated in the system as tested.
     Answer:   NO.
   2. The test sponsor attests that CVE-2017-5753 (Spectre variant 1) is mitigated in the system as tested.
     Answer:   NO.
   3. The test sponsor attests that CVE-2017-5715 (Spectre variant 2) is mitigated in the system as tested.
     Answer:   NO.

</pre>

]]>
</firmware>

</flagsdescription>
