Date: Wed Jul 26 07:35:39 PM EDT 2023
Test set: performance
Kernel: 6.4.6-200.0.riscv64.fc38.riscv64
Release: Fedora release 38 (Thirty Eight)
Result: PASS
Failed Tests: None
Warned Tests: None
============================================================
Starting test ./performance/lmbench3
cd src && make
make[1]: Entering directory '/home/riscv/kernel-tests/performance/lmbench3/src'
gmake[2]: Entering directory '/home/riscv/kernel-tests/performance/lmbench3/src'
gmake[2]: Nothing to be done for 'all'.
gmake[2]: Leaving directory '/home/riscv/kernel-tests/performance/lmbench3/src'
gmake[2]: Entering directory '/home/riscv/kernel-tests/performance/lmbench3/src'
gmake[2]: Nothing to be done for 'opt'.
gmake[2]: Leaving directory '/home/riscv/kernel-tests/performance/lmbench3/src'
make[1]: Leaving directory '/home/riscv/kernel-tests/performance/lmbench3/src'
cd src && make results
make[1]: Entering directory '/home/riscv/kernel-tests/performance/lmbench3/src'
gmake[2]: Entering directory '/home/riscv/kernel-tests/performance/lmbench3/src'
gmake[2]: Nothing to be done for 'all'.
gmake[2]: Leaving directory '/home/riscv/kernel-tests/performance/lmbench3/src'
gmake[2]: Entering directory '/home/riscv/kernel-tests/performance/lmbench3/src'
gmake[2]: Nothing to be done for 'opt'.
gmake[2]: Leaving directory '/home/riscv/kernel-tests/performance/lmbench3/src'
=====================================================================

		L M B E N C H   C ON F I G U R A T I O N
		----------------------------------------

You need to configure some parameters to lmbench.  Once you have configured
these parameters, you may do multiple runs by saying

	"make rerun"

in the src subdirectory.

NOTICE: please do not have any other activity on the system if you can
help it.  Things like the second hand on your xclock or X perfmeters
are not so good when benchmarking.  In fact, X is not so good when
benchmarking.

=====================================================================

Hang on, we are calculating your timing granularity.
OK, it looks like you can time stuff down to 1000000 usec resolution.

Hang on, we are calculating your timing overhead.
OK, it looks like your gettimeofday() costs 0 usecs.

Hang on, we are calculating your loop overhead.
OK, it looks like your benchmark loop costs 0.00000000 usecs.

=====================================================================

If you are running on an MP machine and you want to try running
multiple copies of lmbench in parallel, you can specify how many here.

Using this option will make the benchmark run 100x slower (sorry).

NOTE:  WARNING! This feature is experimental and many results are 
	known to be incorrect or random!

MULTIPLE COPIES [default 1] Options to control job placement
1) Allow scheduler to place jobs
2) Assign each benchmark process with any attendent child processes
   to its own processor
3) Assign each benchmark process with any attendent child processes
   to its own processor, except that it will be as far as possible
   from other processes
4) Assign each benchmark and attendent processes to their own
   processors
5) Assign each benchmark and attendent processes to their own
   processors, except that they will be as far as possible from
   each other and other processes
6) Custom placement: you assign each benchmark process with attendent
   child processes to processors
7) Custom placement: you assign each benchmark and attendent
   processes to processors

Note: some benchmarks, such as bw_pipe, create attendent child
processes for each benchmark process.  For example, bw_pipe
needs a second process to send data down the pipe to be read
by the benchmark process.  If you have three copies of the
benchmark process running, then you actually have six processes;
three attendent child processes sending data down the pipes and 
three benchmark processes reading data and doing the measurements.

Job placement selection: =====================================================================

Several benchmarks operate on a range of memory.  This memory should be
sized such that it is at least 4 times as big as the external cache[s]
on your system.   It should be no more than 80% of your physical memory.

The bigger the range, the more accurate the results, but larger sizes
take somewhat longer to run the benchmark.

MB [default 1361] Checking to see if you have 1361 MB; please wait for a moment...
../scripts/config-run aborted: Not enough memory, only 1MB available.
make[1]: Leaving directory '/home/riscv/kernel-tests/performance/lmbench3/src'

                 L M B E N C H  3 . 0   S U M M A R Y
                 ------------------------------------
		 (Alpha software, do not distribute)