SunVTS 6.4 Test Reference Manual for x86 Platforms
|
![Table Of Contents Table Of Contents](shared/toc01.gif) ![Previous Chapter Previous Chapter](shared/prev01.gif) ![Next Chapter Next Chapter](shared/next01.gif)
|
cputest Description
The cputest checks specific aspects of processor datapath functionality.
The cputest comprises two subtests:
- g0 subtest - This subtest is not supported on x86 platforms.
- CUC subtest - Tests a processor's ability to correctly execute a Compress/Uncompress/Compare (cmp) command sequence.
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.
|
Caution - Do not run the CUC subtest with the retention mode set to savefor numerous passes, otherwise the files that are saved in /tmp/sunvtscan fill the
/tmpcapacity. If /tmpis mounted to the swap area, the swap space may become filled to capacity.
|
Note - Only one instance of cputest per processor is possible.
|
Note - 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.
|
Note - SunVTS does not support processor sets. If processor sets are defined, you must first delete the processor sets before running SunVTS.
|
cputest Options
To reach the following dialog box, 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 might not include the device appropriate to this test. Refer to the SunVTS User's Guide for more details.
FIGURE 4-1 cputestTest Parameter Options Dialog Box
TABLE 4-1 cputest Option Dialog Box Descriptions
Option
|
Description
|
Iterations
|
Specifies the number of times to loop on the selected subtests. Use the up and down arrow keys to select a value from 1 to 8192. The default varies depending on the SunVTS test mode.
|
Test List
|
Specifies which subtests to run. The choices are:
- CUC - The compress/uncompress/compare subtest.
Refer to the general test description at the beginning of this chapter for subtest descriptions. If no subtest is selected, both subtests run.
|
File Size (KBytes)
|
Specifies the size of the CUC pattern file in KBytes. Select a value from 1 to 8192. The default varies depending on the SunVTS test mode.
|
File Retention Mode
|
Specifies whether the cputest removes the CUC pattern files or not. The choices are:
- Purge - Unconditionally removes the four subtest files.
- Save - Does not remove any of the four subtest files.
- OnError - Removes the four subtest files unless the CUC resulted in a miscompare. In this case, do not remove the files.
The default is OnError.
Refer to the Caution at the beginning of this chapter regarding the Save value.
|
Processor Affinity
|
Although the Test Parameter Options dialog box displays the processor affinity Bound To selection box, the processor that corresponds to this instance of the cputest is determined when the SunVTS kernel probes for devices. Therefore, switching processor affinity in this dialog box is not supported.
|
cputest Test Modes
The following table describes how the cputest functions in the different test modes.
TABLE 4-2 cputest Supported Test Modes
Test Mode
|
Description
|
Connection
|
Both subtests are selected. The test options are fixed with the following values:
- Iterations=5
- File Size=64 KBytes
- File retention=OnError
|
Functional
|
Both subtests are selectable, and all the test options are available to scale the cputest as needed.
|
Online
|
Supported.
|
cputest Command-Line Syntax
/opt/SUNWvts/bin/cputest standard-arguments -o dev=device-name,count=count-number,test=testlist,size=file-size,retain=mode
TABLE 4-3 cputest Command-Line Syntax
Argument
|
Description
|
dev=device-name
|
Specifies the name of the device to test, for example, cpu-unit5
|
count=count-number
|
Defines the number of times to loop on the subtests. Use a number from 1 to 8192. The default is 200.
|
test=testlist
|
Specifies which subtests to run. The choices are:
|
size=file-size
|
Specifies the size of the CUC pattern file in KBytes. Select a value from 1 to 8192. The default is 1024.
|
retain=mode
|
Specifies whether the cputest removes the CUC pattern files or not. The choices are:
- Purge - unconditionally remove the four subtest files
- Save - do not remove any of the four subtest files
- OnError - remove the four subtest files unless the CUC resulted in a miscompare. In this case do not remove the files.
The default is OnError.
Refer to the Caution at the beginning of this chapter regarding the Save value.
|
SunVTS 6.4 Test Reference Manual for x86 Platforms
|
820-1671-10
|
![Table Of Contents Table Of Contents](shared/toc01.gif) ![Previous Chapter Previous Chapter](shared/prev01.gif) ![Next Chapter Next Chapter](shared/next01.gif)
|
Copyright © 2007, Sun Microsystems, Inc. All Rights Reserved.