Core
The core test detects clock jitter and performs a comprehensive CPU stress test. You can run this test to verify that your system CPUs function correctly and maintain synchronization under heavy computing loads.
- What the test covers
- The core test examines the system’s CPUs and ensures that they are capable of functioning properly under load.
- RHEL version supported
-
- RHEL 8
- RHEL 9
- RHEL 10
- What the test does
-
The core test is composed of two separate routines. The first routine detects clock jitter. Jitter occurs when the system clocks fall out of sync with each other.
System clocks differ from CPU clock speed. Clock speed refers to the rate at which the CPUs operate.
The jitter test uses the getimeofday() function to record the time observed by each logical CPU. It then analyzes the returned values. The test passes if all CPU clocks stay within .2 nanoseconds of each other.
The jitter test tolerances are very tight. Good results require that rhcert tests are the only loads running on the system. This must be true while the test runs.
Any other compute load can interfere with the timing and cause the test to fail. The jitter test also checks which clock source the kernel uses.
It logs a warning if an Intel processor does not use TSC. This warning does not affect the test’s PASS or FAIL status.
The second routine is a CPU load test. The required stress package provides this test. You can also use the stress program outside the rhcert suite to stress test a system.
It launches several simultaneous activities on the system. It then monitors for failures. It instructs each logical CPU to calculate square roots.
It also stresses system memory by using malloc() and free() to reserve and free memory. Finally, it forces disk writes by calling sync().
These activities run for 10 minutes, and the test passes if no failures occur. See the stress manpage if you want to use it outside of hardware certification testing.
- Preparing for the test
- The only preparation for the core test is to install a CPU. This CPU must meet the requirements stated in the Policy Guide.
- Running the test
-
The core test is non-interactive. Run the following command and then select the appropriate
Coretest name from the list that displays.rhcert-run - Run time, bare-metal
- The core test itself takes about 12 minutes to run on a bare-metal system. The jitter portion of the test takes a minute or two and the stress portion runs for exactly 10 minutes. The required supportable test adds about a minute to the overall run time.
- Run time, full-virt guest
- The fv_core test takes about 14 minutes in a KVM guest, slightly longer than bare-metal. The added time is due to guest startup/shutdown activities and the required supportable test that runs in the guest. The required supportable test on the bare-metal system adds about a minute to the overall run time.