about summary refs log tree commit diff
path: root/docs/FAQ.md
diff options
context:
space:
mode:
authorvanhauser-thc <vh@thc.org>2021-12-29 10:57:37 +0100
committervanhauser-thc <vh@thc.org>2021-12-29 10:57:37 +0100
commit0792cab5661271250218f6b83b2298e491191e67 (patch)
tree2f6cb4361e9a91a53e714273fab8abe11d8e60f9 /docs/FAQ.md
parentb5cb99f6fe84603d4bc896a2d56b9ad1e86779f6 (diff)
downloadafl++-0792cab5661271250218f6b83b2298e491191e67.tar.gz
add power schedule info
Diffstat (limited to 'docs/FAQ.md')
-rw-r--r--docs/FAQ.md21
1 files changed, 21 insertions, 0 deletions
diff --git a/docs/FAQ.md b/docs/FAQ.md
index f1cffe00..3d3dce20 100644
--- a/docs/FAQ.md
+++ b/docs/FAQ.md
@@ -180,6 +180,27 @@ If you find an interesting or important question missing, submit it via
   [best_practices.md#improving-stability](best_practices.md#improving-stability).
 </p></details>
 
+<details>
+  <summary id="what-are-power-schedules">What are power schedules?</summary><p>
+
+  Not every item in our queue/corpus is the same, some are more interesting,
+  others provide little value.
+  A power schedule measures how "interesting" a value is, and depending on
+  the calculated value spends more or less time mutating it.
+
+  AFL++ comes with several power schedules, initially ported from [AFLFast](https://github.com/mboehme/aflfast)
+  however modified to be more effective and several more modes added.
+
+  The most effective modes are '-p fast` (default) and `-p explore`.
+
+  If you fuzz with several parallel afl-fuzz instances, then it is beneficial
+  to assign a different schedule to each instance, however the majority should
+  be `fast` and `explore`.
+
+  It does not make sense to explain the details of the calculation and
+  reasoning behind all of the schedules. If you are interested, read the source
+  code and the AFLFast paper.
+
 ## Troubleshooting
 
 <details>