The cputest checks specific aspects of SPARC V9 processor datapath functionality.
The cputest comprises two subtests:
g0 subtest--tests a processor's g0 register functionality. The g0 subtest is only supported on UltraSPARC-based systems.
CUC subtest--tests a processor's ability to correctly execute a Compress/Uncompress/Compare (cmp) command sequence on machines with the SPARC-V9 architecture. As the CUC subtest runs, it creates four files in the /tmp/sunvts directory. The CUC subtest uses the following file naming conventions where nnn represents the processor unit number and x represents a random character string appended to the file name:
PnnnPx-- original pattern file (size determined by the cputest File Size option)
PnnnZx-- compressed version of the pattern file
PnnnUx-- uncompressed data from the PnnnZx file
PnnnCx-- comparison data between the PnnnPx and PnnnUx files
With the cputest file retention mode, you can control whether these files are deleted or not, so that in the event of a miscompare, you can view the contents of the files to analyze the miscompared data. The exact names of the files are displayed in the SunVTS message window whenever the files are saved such as when there is a compression miscompare or when the file retention mode is set to save. Refer to "cputest Options" for more details.
Do not run the CUC subtest with the retention mode set to save for numerous passes, otherwise the files that are saved in /tmp/sunvts can fill the /tmp capacity. If /tmp is mounted to the swap area, the swap space may become filled to capacity.
Only one instance of cputest per processor is possible.
When cputest is run with other tests, it may give the error message "exec'd program compress failed with code 1". This can be an indication of a failed compression program, not necessarily a failed CPU. If this occurs, stop all other tests and run cputest alone. If the message occurs again, the CPU is failing.
The cputest only runs on SPARC V9 systems.
To reach the dialog box below, right-click on the test name in the System Map and select Test Parameter Options. If you do not see this test in the System Map, you might need to expand the collapsed groups, or your system may not include the device appropriate to this test. Refer to the SunVTS User's Guide for more details.
The following table describes how the cputest functions in the different test modes.
Table 10-2 cputest Test Modes
/opt/SUNWvts/bin/cputest standard_arguments -o dev=device_name,count=count_number,test=testlist,size=file_size,retain=mode
Table 10-3 cputest Command-Line Syntax
64-bit tests are located in the sparcv9 subdirectory: /opt/SUNWvts/bin/sparcv9/testname. If a test is not present in this directory, then it may only be available as a 32-bit test. For more information refer to "32-Bit and 64-Bit Tests".