X-Git-Url: https://git.libre-soc.org/?a=blobdiff_plain;f=TESTING.md;h=17aeff94c4a59e4ccc117a5c3c975bf633aa2e5a;hb=75e7f18e80351e12e1b828b6e077f3ec1d5ace1b;hp=cf160e609bc30abb2f469f328eeb0cefe4291ad4;hpb=c3a4fb0c568294c8ea2268336e45d3d02dbdd5cd;p=gem5.git

diff --git a/TESTING.md b/TESTING.md
index cf160e609..17aeff94c 100644
--- a/TESTING.md
+++ b/TESTING.md
@@ -1,6 +1,3 @@
-:Authors: Jason Lowe-Power
-          Sean Wilson
-
 This file explains how to use gem5's updated testing infrastructure. Running
 tests before submitting a patch is *incredibly important* so unexpected bugs
 don't creep into gem5.
@@ -197,16 +194,23 @@ if the file causes an exception. This means there are no tests in that file
 
 ## Binary test applications
 
-The code for test binaries that are run in the gem5 guest during testing are
-found in `tests/test-progs`.
+The code for some test binaries that are run in the gem5 guest during
+testing can be found in `tests/test-progs`.
 There's one directory per test application.
 The source code is under the `source` directory.
 
 You may have a `bin` directory as well.
 The `bin` directory is automatically created when running the test case that
-uses the test binary. The binary is downloaded from the gem5 servers the first
+uses the test binary.
+This is not the case when a test is run via the --bin-path option.
+In that scenario a bin directory will be created in the selected path
+rather than in `tests/test-progs`.
+The binary is downloaded from the gem5 servers the first
 time it is referenced by a test.
 
+Some other tests (like Linux-boot) don't have sources inside gem5 and
+are simply downloaded from gem5 servers.
+
 ## Updating the test binaries
 
 The test infrastructure should check with the gem5 servers to ensure you have