|
bgpattern
|
Enhanced for UltraSPARC T1 (high-end processor with chip multithreading [CMT]) based systems to use background patterns to work as the base patterns for read/write operations within the march test selected. This technique has proven to be very effective and useful for l2sram tests that use similar pattern generation techniques. You can, however, still use the previous methods.
|
|
reserve
|
Specifies the amount of memory that will not be allocated for testing. reserve represents a percentage of the total physical memory in the system. When the test starts, it probes the total memory present in the system, then tries to allocate (100 - reserve)% of memory. If the allocation or locking does not succeed the amount of memory is reduced before the retry. Before starting the test, the amount of memory allocated for testing is displayed.
Default value for reserve option is 20. For UltraSPACR IIIi platforms, the default value is 25.
On low memory systems, keep the reserve value higher to avoid excessive swapping.
For 32-bit booted systems, the reserve value represents the percentage of 4 GB rather than the percentage of total physical memory.
|
|
stride
|
By default stride is set to random. It can be set to Column or Row also. For random, either Row or Column are randomly selected for each pass. The value of stride defines the memory locations addressed consecutively in certain subtests, in a hardware dependent manner. All testable memory is still tested. Using different stride checks coupling among a different set of memory cells, therefore random is the recommended value for this option unless both Column and Row are being explicitly used in different instances. For FA type of uses, stride may also be set to UserDefined, in this case the test will stride the number of banks specified in the userstride option.
stride may be set to Custom in which case the stride values are randomly selected from the strides specified in the stridemask value.
|
|
userstride
|
Use this option to set number of banks the test should stride. One of the good choices could be the interleave on the suspect bank, during FA. the value is limited between 1 and 16. This also means row striding is not possible while using this option.
|
|
stridemask
|
When stride=custom is selected, this value specifies the strides used. Each thread selects one of the stride values from stridemask by selecting one of the bits in the mask.
The bits in the stridemask value represent the Least Significant bit of the stride. Thus a value of 0x4000 calls for a stride of 16384 (using bit 14 of the address). Mulitple bits can be set by mixing row and column strides.
The value can be specified as a decimal (NNN), hexadecimal (0xNNN), or octal (0NNN) value. The maximum value is 0x400000 (4194304). The default value is 0xC600 which represents strides using Bits 15, 14, 10, and 9.
|
|
lock
|
By default memory locking is disabled. To turn it on set the lock to enabled. The test uses ISM to lock the memory into the core, this gives 4 MB virtual pages and avoids swapping. Running without locking adds more randomness to the addressing sequence.
If memory locking with ISM fails, the test allocates on heap and tries to lock the memory allocated on heap.
On low memory systems, this option can be enabled to avoid excessive swapping.
Solaris 10 users, perform the following steps:
1. Issue the following command:
% prctl $$
If resource controls project.max-shm-memory and project.max-shm-ids are listed in the output, proceed to the next step, otherwise follow the instructions given for Solaris 9.
2. Retrieve the default project with the following command:
% projects -d root
This command outputs the default project name, project1 in this example, for the Super User.
3. Set the resource control project.max-shm-memory with the following command:
% prctl -t privileged -r -n \
project.max-shm-memory -v 9223372036854775807 \
-i project project1
For further information please refer to the Solaris Tunable Parameters Reference Manual applicable to your Solaris release.
|
|
eccmonitor
|
ECC Monitor is enabled by default. The ECC error monitor runs as a separate thread in the test. When an ECC error is detected, the message is displayed on to the test output. The monitor can be turned off by setting this option to disabled.
|
|
threshold
|
Number of ECC errors after which the test stops (if ECC monitor is running). When the threshold is reached the test will exit with a non zero exit code. If set to zero, the test will still report all the errors but will not stop. The default threshold is 2.
|
|
pass
|
Specifies the number of passes in the single instance. Increase pass if lock is enabled. This saves time spent on locking the memory when a new process or instance is spawned by the SunVTS kernel. This pass has no relation with the system passes in the SunVTS infrastructure, it will appear that ramtest is taking longer to complete system passes.
|
|
ntaloops
|
Specifies number of loops of NTA march(30N) test, per pass. Increasing the number of loops of any subtest increases the relative time spent on that subtest in each pass. This increase also increases the time taken to complete a pass. NTA march test attacks stuck-at-faults, two-cell coupling faults, and some three-cell coupling faults.
|
|
laloops
|
Specifies number of loops of LA march(22N) test, per pass. Increasing the number of loops of any subtest increases the relative time spent on that subtest in each pass. This increase also increases the time taken to complete a pass. LA march test attacks coupling and stuck-at-faults.
|
|
ntaloops
|
Specifies number of loops of NTA march test, per pass. Increasing the number of loops of any subtest increases the relative time spent on that subtest in each pass. This increase also increases the time taken to complete a pass. NTA march test attacks coupling and stuck at faults.
|
|
lrloops
|
Specifies number of loops of LR march(14N) test, per pass. Increasing the number of loops of any subtest increases the relative time spent on that subtest in each pass. This increase also increases the time taken to complete a pass. LR march test attacks coupling and stuck-at-faults.
|
|
dratio
|
(Descramble ratio) Tunes the algorithm used to generate data patterns in ramtest. A descramble ratio of 100 means that all the data patterns generated will be descrambled. If a descramble ratio is 0, the test will generate the data patterns tuned toward bus noise. Default value is 50, which means that half the data patterns are descrambled.
|
|
ssloops
|
Specifies number of loops of SS march(22N) test, per pass. Increasing the number of loops of any subtest increases the relative time spent on that subtest in each pass. This increase also increases the time taken to complete a pass. The SS March test attacks simple static faults.
|
|
custom
|
When stride=custom is selected, this value specifies the strides used. Each thread selects one of the stride values from stridemask by selecting one of the bits in the mask.
The bits in the stridemask value represent the least significant bit of the stride. Thus a value of 0x4000 calls for a stride of 16384 (using Bit 14 of the address). Mulitple bits can be set mixing row and column strides.
The value can be specified as a decimal (NNN), hexadecimal (0xNNN), or octal (0NNN) value. The maximum value is 0x400000 (4194304). The default value is 0xC600 which represents strides using Bits 15, 14, 10, and 9.
|
