diff --git a/tests/gem5/arm_boot_tests/README.md b/tests/gem5/arm_boot_tests/README.md
new file mode 100644
index 0000000000..68d5de97f1
--- /dev/null
+++ b/tests/gem5/arm_boot_tests/README.md
@@ -0,0 +1,9 @@
+# Arm Boot Tests
+
+These tests run a series of Linux boots on the ARMBoard.
+It varies the CPU type, number of CPUs, and memory used for each run.
+To run these tests by themselves, you can run the following command in the tests directory:
+
+```bash
+./main.py run gem5/arm_boot_tests --length=[length]
+```
diff --git a/tests/gem5/asmtest/README.md b/tests/gem5/asmtest/README.md
new file mode 100644
index 0000000000..fcbe8ea65c
--- /dev/null
+++ b/tests/gem5/asmtest/README.md
@@ -0,0 +1,9 @@
+# ASM Test
+
+These tests run a set of RISCV binaries on a bare bones syscall execution.
+In addition, these test run these binaries against different CPU types.
+To run these tests by themselves, you can run the following command in the tests directory:
+
+```bash
+./main.py run gem5/asmtest --length=[length]
+```
diff --git a/tests/gem5/cpu_tests/README.md b/tests/gem5/cpu_tests/README.md
new file mode 100644
index 0000000000..574d12ce0a
--- /dev/null
+++ b/tests/gem5/cpu_tests/README.md
@@ -0,0 +1,8 @@
+# CPU Tests
+
+These tests run the Bubblesort and FloatMM workloads against the different CPU models.
+To run these tests by themselves, you can run the following command in the tests directory:
+
+```bash
+./main.py run gem5/cpu_tests --length=[length]
+```
diff --git a/tests/gem5/dram_lowp/README.md b/tests/gem5/dram_lowp/README.md
new file mode 100644
index 0000000000..bff3f033fd
--- /dev/null
+++ b/tests/gem5/dram_lowp/README.md
@@ -0,0 +1,8 @@
+# DRAM LowP
+
+These tests run the `configs/dram` scripts that trigger low power state transitions in the DRAM controller.
+To run these tests by themselves, you can run the following command in the tests directory:
+
+```bash
+./main.py run gem5/dram_lowp --length=[length]
+```
diff --git a/tests/gem5/fs/linux/arm/README.md b/tests/gem5/fs/linux/arm/README.md
new file mode 100644
index 0000000000..ba4bf07b36
--- /dev/null
+++ b/tests/gem5/fs/linux/arm/README.md
@@ -0,0 +1,8 @@
+# FS
+
+This is a set of full system ARM tests.
+To run these tests by themselves, you can run the following command in the tests directory:
+
+```bash
+./main.py run gem5/fs/linux/arm --length=[length]
+```
diff --git a/tests/gem5/gem5_library_example_tests/README.md b/tests/gem5/gem5_library_example_tests/README.md
new file mode 100644
index 0000000000..3abba289f7
--- /dev/null
+++ b/tests/gem5/gem5_library_example_tests/README.md
@@ -0,0 +1,8 @@
+# gem5 Library Example Tests
+
+This set of tests checks the examples in `configs/example/gem5_library`, and makes sure they run to completion.
+To run these tests by themselves, you can run the following command in the tests directory:
+
+```bash
+./main.py run gem5/gem5-resources --length=very-long
+```
diff --git a/tests/gem5/gem5_resources/README.md b/tests/gem5/gem5_resources/README.md
new file mode 100644
index 0000000000..8243c01b9f
--- /dev/null
+++ b/tests/gem5/gem5_resources/README.md
@@ -0,0 +1,8 @@
+# gem5 Resources
+
+This test makes sure that resources you download within gem5 work properly, and the downloaded resource matches the input given.
+To run these tests by themselves, you can run the following command in the tests directory:
+
+```bash
+./main.py run gem5/gem5_resources --length=very-long
+```
diff --git a/tests/gem5/gpu/README.md b/tests/gem5/gpu/README.md
new file mode 100644
index 0000000000..9722e30161
--- /dev/null
+++ b/tests/gem5/gpu/README.md
@@ -0,0 +1,8 @@
+# GPU
+
+These tests do random checks to the Ruby GPU protocol within gem5.
+To run these tests by themselves, you can run the following command in the tests directory:
+
+```bash
+./main.py run gem5/gem5-resources --length=very-long
+```
diff --git a/tests/gem5/insttest_se/README.md b/tests/gem5/insttest_se/README.md
new file mode 100644
index 0000000000..3895316674
--- /dev/null
+++ b/tests/gem5/insttest_se/README.md
@@ -0,0 +1,8 @@
+# Inst Test SE
+
+These test the insttest binary running on the SPARC ISA, checking against different CPU models.
+To run these tests by themselves, you can run the following command in the tests directory:
+
+```bash
+./main.py run gem5/insttest_se --length=[length]
+```
diff --git a/tests/gem5/kvm_fork_tests/README.md b/tests/gem5/kvm_fork_tests/README.md
new file mode 100644
index 0000000000..5d2d8e8ff8
--- /dev/null
+++ b/tests/gem5/kvm_fork_tests/README.md
@@ -0,0 +1,8 @@
+# KVM Fork Tests
+
+These tests check that gem5 can fork with the KVM cpu, then switch to a different CPU.
+To run these tests by themselves, you can run the following command in the tests directory:
+
+```bash
+./main.py run gem5/kvm_fork_tests --length=[length]
+```
diff --git a/tests/gem5/kvm_switch_tests/README.md b/tests/gem5/kvm_switch_tests/README.md
new file mode 100644
index 0000000000..9a46aa6c8b
--- /dev/null
+++ b/tests/gem5/kvm_switch_tests/README.md
@@ -0,0 +1,8 @@
+# KVM Switch Tests
+
+These tests ensure that gem5 can switch processors during simulation.
+To run these tests by themselves, you can run the following command in the tests directory:
+
+```bash
+./main.py run gem5/kvm_switch_tests --length=[length]
+```
diff --git a/tests/gem5/learning_gem5/README.md b/tests/gem5/learning_gem5/README.md
new file mode 100644
index 0000000000..eda68d9d4c
--- /dev/null
+++ b/tests/gem5/learning_gem5/README.md
@@ -0,0 +1,9 @@
+# Learning gem5
+
+This set of tests ensures that the example scripts for the gem5 tutorial run properly.
+
+To run these tests by themselves, you can run the following command in the tests directory:
+
+```bash
+./main.py run gem5/learning_gem5 --length=[length]
+```
diff --git a/tests/gem5/m5_util/README.md b/tests/gem5/m5_util/README.md
new file mode 100644
index 0000000000..133345a904
--- /dev/null
+++ b/tests/gem5/m5_util/README.md
@@ -0,0 +1,8 @@
+# m5 Util
+
+These test the util m5 exit assembly instruction.
+To run these tests by themselves, you can run the following command in the tests directory:
+
+```bash
+./main.py run gem5/m5_util --length=[length]
+```
diff --git a/tests/gem5/m5threads_test_atomic/README.md b/tests/gem5/m5threads_test_atomic/README.md
new file mode 100644
index 0000000000..5e52b91958
--- /dev/null
+++ b/tests/gem5/m5threads_test_atomic/README.md
@@ -0,0 +1,8 @@
+# m5 Threads Test Atomic
+
+These are m5threads atomic tests that run against different CPU types.
+To run these tests by themselves, you can run the following command in the tests directory:
+
+```bash
+./main.py run gem5/m5threads_test_atomic --length=[length]
+```
diff --git a/tests/gem5/memory/README.md b/tests/gem5/memory/README.md
new file mode 100644
index 0000000000..892593394d
--- /dev/null
+++ b/tests/gem5/memory/README.md
@@ -0,0 +1,9 @@
+# Memory
+
+These run a set of tests on memory within gem5.
+
+To run these tests by themselves, you can run the following command in the tests directory:
+
+```bash
+./main.py run gem5/memory --length=[length]
+```
diff --git a/tests/gem5/multi_isa/README.md b/tests/gem5/multi_isa/README.md
new file mode 100644
index 0000000000..94d8c1a3e1
--- /dev/null
+++ b/tests/gem5/multi_isa/README.md
@@ -0,0 +1,9 @@
+# Multi ISA
+
+These tests check that all our ISAs are both currrently supported within gem5, as well as checking that get_runtime_isa() works as expected.
+
+To run these tests by themselves, you can run the following command in the tests directory:
+
+```bash
+./main.py run gem5/multi_isa --length=[length]
+```
diff --git a/tests/gem5/parsec_benchmarks/README.md b/tests/gem5/parsec_benchmarks/README.md
new file mode 100644
index 0000000000..90dfd5a8e8
--- /dev/null
+++ b/tests/gem5/parsec_benchmarks/README.md
@@ -0,0 +1,9 @@
+# Parsec Benchmarks
+
+These tests run through a subset of the parsec benchmarks within gem5.
+
+To run these tests by themselves, you can run the following command in the tests directory:
+
+```bash
+./main.py run gem5/parsec_benchmarks --length=[length]
+```
diff --git a/tests/gem5/riscv_boot_tests/README.md b/tests/gem5/riscv_boot_tests/README.md
new file mode 100644
index 0000000000..002cc4d09d
--- /dev/null
+++ b/tests/gem5/riscv_boot_tests/README.md
@@ -0,0 +1,9 @@
+# RISCV Boot Tests
+
+These tests run a series of Linux boots on the RISCVBoard.
+It varies the CPU type, number of CPUs, and memory used for each run.
+To run these tests by themselves, you can run the following command in the tests directory:
+
+```bash
+./main.py run gem5/riscv_boot_tests --length=[length]
+```
diff --git a/tests/gem5/se_mode/hello_se/README.md b/tests/gem5/se_mode/hello_se/README.md
new file mode 100644
index 0000000000..b3109692b0
--- /dev/null
+++ b/tests/gem5/se_mode/hello_se/README.md
@@ -0,0 +1,8 @@
+# SE Mode
+
+These tests use the SimpleBoard to test simple binaries in SE mode, both with single and multi cores.
+To run these tests by themselves, you can run the following command in the tests directory:
+
+```bash
+./main.py run gem5/se_mode/hello_se --length=[length]
+```
diff --git a/tests/gem5/stats/README.md b/tests/gem5/stats/README.md
new file mode 100644
index 0000000000..c55600bed1
--- /dev/null
+++ b/tests/gem5/stats/README.md
@@ -0,0 +1,8 @@
+# Stats
+
+This test runs an SE simulation with the hdf5 stats and checks that the simulation succeeds and the stats file exists.
+To run these tests by themselves, you can run the following command in the tests directory:
+
+```bash
+./main.py run gem5/stats --length=[length]
+```
diff --git a/tests/gem5/stdlib/README.md b/tests/gem5/stdlib/README.md
new file mode 100644
index 0000000000..0b0649f6b6
--- /dev/null
+++ b/tests/gem5/stdlib/README.md
@@ -0,0 +1,8 @@
+# Standard Library
+
+These tests check that the BaseCPUProcessor and the gem5.utils.requires function work as intended.
+To run these tests by themselves, you can run the following command in the tests directory:
+
+```bash
+./main.py run gem5/stdlib --length=[length]
+```
diff --git a/tests/gem5/to_tick/README.md b/tests/gem5/to_tick/README.md
new file mode 100644
index 0000000000..e675905120
--- /dev/null
+++ b/tests/gem5/to_tick/README.md
@@ -0,0 +1,8 @@
+# To Tick
+
+These tests check that setting the max tick in various ways behaves as expected, as well as that event scheduling at a certain tick works.
+To run these tests by themselves, you can run the following command in the tests directory:
+
+```bash
+./main.py run gem5/to_tick --length=[length]
+```
diff --git a/tests/gem5/traffic_gen/README.md b/tests/gem5/traffic_gen/README.md
new file mode 100644
index 0000000000..dadb71b641
--- /dev/null
+++ b/tests/gem5/traffic_gen/README.md
@@ -0,0 +1,9 @@
+# Traffic Generator
+
+This tests the gem5 memory components with a simple traffic generator.
+It also checks the correctness of the statistics outputted by gem5.
+To run these tests by themselves, you can run the following command in the tests directory:
+
+```bash
+./main.py run gem5/traffic_gen --length=[length]
+```
diff --git a/tests/gem5/x86_boot_tests/README.md b/tests/gem5/x86_boot_tests/README.md
new file mode 100644
index 0000000000..92357b6bb2
--- /dev/null
+++ b/tests/gem5/x86_boot_tests/README.md
@@ -0,0 +1,9 @@
+# X86 Boot Tests
+
+These tests run a series of Linux boots on the X86Board.
+It varies the CPU type, number of CPUs, and memory used for each run.
+To run these tests by themselves, you can run the following command in the tests directory:
+
+```bash
+./main.py run gem5/x86_boot_tests --length=[length]
+```