deploy: 69b948f

commands/runbms.html

@@ -184,7 +184,7 @@ <h2 id="usage"><a class="header" href="#usage">Usage</a></h2>
 <p><code>-s</code>: only use the specified heap sizes.
 This is a comma-separated string of integers or floating point numbers.
 For each slice <code>s</code> in <code>SLICE</code>, we run benchmarks at <code>s * minheap</code>.
-<code>N</code> and <code>n</code>s are ignored. </p>
+<code>N</code> and <code>n</code>s are ignored.</p>
 <p><code>-p</code>: add a prefix to the folder names where the results are stored.
 By default, the folder that stores the result is named using the host name and the timestamp.
 However, you can add a prefix to the folder name to signify which experiments the results belong to.</p>
@@ -230,7 +230,7 @@ <h3 id="zulip"><a class="header" href="#zulip"><code>Zulip</code></a></h3>
     type: Zulip
     request:
       type: private
-      to: [&quot;your user id here&quot;]
+      to: ["your user id here"]
 </code></pre>
 <h4 id="keys-1"><a class="header" href="#keys-1">Keys</a></h4>
 <p><code>request</code>: please follow the <a href="https://zulip.com/api/send-message">Zulip API documentation</a>.
@@ -250,7 +250,7 @@ <h3 id="copyfile"><a class="header" href="#copyfile"><code>CopyFile</code></a></
   dacapo_latency:
     type: CopyFile
     patterns:
-      - &quot;scratch/dacapo-latency-*.csv&quot;
+      - "scratch/dacapo-latency-*.csv"
 </code></pre>
 <h4 id="keys-2"><a class="header" href="#keys-2">Keys</a></h4>
 <p><code>patterns</code>: a list of patterns following the Python 3 <code>pathlib.Path.glob</code> <a href="https://docs.python.org/3/library/pathlib.html#pathlib.Path.glob">syntax</a>.

cookbook/perf_events.html

@@ -185,39 +185,39 @@ <h2 id="jvmti"><a class="header" href="#jvmti">JVMTI</a></h2>
 <pre><code class="language-yaml">modifiers:
   jvmti_env:
     type: EnvVar
-    var: &quot;LD_PRELOAD&quot;
-    val: &quot;/path/to/distillation/libperf_statistics.so&quot;
+    var: "LD_PRELOAD"
+    val: "/path/to/distillation/libperf_statistics.so"
 </code></pre>
 <p>Second, you need to specify a list of events you want to measure.</p>
 <pre><code class="language-yaml">modifiers:
   perf:
     type: EnvVar
-    var: &quot;PERF_EVENTS&quot;
-    val: &quot;PERF_COUNT_HW_CPU_CYCLES,PERF_COUNT_HW_INSTRUCTIONS,PERF_COUNT_HW_CACHE_LL:MISS,PERF_COUNT_HW_CACHE_L1D:MISS,PERF_COUNT_HW_CACHE_DTLB:MISS&quot;
+    var: "PERF_EVENTS"
+    val: "PERF_COUNT_HW_CPU_CYCLES,PERF_COUNT_HW_INSTRUCTIONS,PERF_COUNT_HW_CACHE_LL:MISS,PERF_COUNT_HW_CACHE_L1D:MISS,PERF_COUNT_HW_CACHE_DTLB:MISS"
 </code></pre>
 <p>If you want to get a full list of events you can use on a particular machine, you can clone and build <a href="https://sourceforge.net/p/perfmon2/libpfm4/ci/master/tree/"><code>libpfm4</code></a> and run the <code>showevtinfo</code> <a href="https://sourceforge.net/p/perfmon2/libpfm4/ci/master/tree/examples/showevtinfo.c">program</a>.</p>
 <p>Third, you need to tell the JVM to load the agent.
 Note that you need to specify the absolute path.</p>
 <pre><code class="language-yaml">modifiers:
   jvmti:
     type: JVMArg
-    val: &quot;-agentpath:/path/to/distillation/libperf_statistics.so&quot;
+    val: "-agentpath:/path/to/distillation/libperf_statistics.so"
 </code></pre>
 <p>Finally, you need to let the DaCapo benchmark inform the start and the end of a benchmark iteration.
 We will reuse the <code>RustMMTk</code> probe here, as the callback functions in the JVMTI agent are also called <code>harness_begin</code> and <code>harness_end</code>.</p>
 <pre><code class="language-yaml">modifiers:
   probes_cp:
     type: JVMClasspath
-    val: &quot;/path/to/probes/out /path/to/probes/out/probes.jar&quot;
+    val: "/path/to/probes/out /path/to/probes/out/probes.jar"
   probes:
     type: JVMArg
-    val: &quot;-Djava.library.path=/path/to/probes/out -Dprobes=RustMMTk&quot;
+    val: "-Djava.library.path=/path/to/probes/out -Dprobes=RustMMTk"
 </code></pre>
 <p>Now, putting it all together, you can define a set of modifiers, and use that set in your config strings.</p>
 <pre><code class="language-yaml">modifiers:
   jvmti_common:
     type: ModifierSet
-    val: &quot;probes|probes_cp|jvmti|jvmti_env|perf&quot;
+    val: "probes|probes_cp|jvmti|jvmti_env|perf"
 </code></pre>
 <h2 id="mmtk"><a class="header" href="#mmtk">MMTk</a></h2>
 <p>Please clone and build <a href="../quickstart.html#prepare-probes"><code>probes</code></a>.
@@ -226,17 +226,17 @@ <h2 id="mmtk"><a class="header" href="#mmtk">MMTk</a></h2>
 <pre><code class="language-yaml">modifiers:
   probes_cp:
     type: JVMClasspath
-    val: &quot;/path/to/probes/out /path/to/probes/out/probes.jar&quot;
+    val: "/path/to/probes/out /path/to/probes/out/probes.jar"
   probes:
     type: JVMArg
-    val: &quot;-Djava.library.path=/path/to/probes/out -Dprobes=RustMMTk&quot;
+    val: "-Djava.library.path=/path/to/probes/out -Dprobes=RustMMTk"
 </code></pre>
 <p>Then, you can specify a list of events you want to measure.</p>
 <pre><code class="language-yaml">modifiers:
   mmtk_perf:
     type: EnvVar
-    var: &quot;MMTK_PHASE_PERF_EVENTS&quot;
-    val: &quot;PERF_COUNT_HW_CPU_CYCLES,0,-1;PERF_COUNT_HW_INSTRUCTIONS,0,-1;PERF_COUNT_HW_CACHE_LL:MISS,0,-1;PERF_COUNT_HW_CACHE_L1D:MISS,0,-1;PERF_COUNT_HW_CACHE_DTLB:MISS,0,-1&quot;
+    var: "MMTK_PHASE_PERF_EVENTS"
+    val: "PERF_COUNT_HW_CPU_CYCLES,0,-1;PERF_COUNT_HW_INSTRUCTIONS,0,-1;PERF_COUNT_HW_CACHE_LL:MISS,0,-1;PERF_COUNT_HW_CACHE_L1D:MISS,0,-1;PERF_COUNT_HW_CACHE_DTLB:MISS,0,-1"
 </code></pre>
 <p>Note that the list is semicolon-separated.
 Each entry consists of three parts, separated by commas.

index.html

@@ -178,7 +178,7 @@ <h1 id="introduction"><a class="header" href="#introduction">Introduction</a></h
 <h2 id="disclaimer"><a class="header" href="#disclaimer">Disclaimer</a></h2>
 <p>At this stage, the focus of this project is driven by the internal use of members from <a href="https://users.cecs.anu.edu.au/~steveb/">Steve Blackburn</a>'s lab.
 If you are a member of the lab, you know what to do if you encounter any issue, and you can ignore the below.</p>
-<p>If you are a member of the public, please kindly note that the project is open-source and documented on a &quot;good-faith&quot; basis.
+<p>If you are a member of the public, please kindly note that the project is open-source and documented on a "good-faith" basis.
 We might not have the time to consider your features requests.
 Please don't be offended if we ignore these.
 Having said that, you are very welcomed to use it, and we will be very pleased if this helps anyone.

intro.html

@@ -178,7 +178,7 @@ <h1 id="introduction"><a class="header" href="#introduction">Introduction</a></h
 <h2 id="disclaimer"><a class="header" href="#disclaimer">Disclaimer</a></h2>
 <p>At this stage, the focus of this project is driven by the internal use of members from <a href="https://users.cecs.anu.edu.au/~steveb/">Steve Blackburn</a>'s lab.
 If you are a member of the lab, you know what to do if you encounter any issue, and you can ignore the below.</p>
-<p>If you are a member of the public, please kindly note that the project is open-source and documented on a &quot;good-faith&quot; basis.
+<p>If you are a member of the public, please kindly note that the project is open-source and documented on a "good-faith" basis.
 We might not have the time to consider your features requests.
 Please don't be offended if we ignore these.
 Having said that, you are very welcomed to use it, and we will be very pleased if this helps anyone.