216         /*
 217          * Exclude JVMCI threads counts from testing similar to other threads counts.
 218          */
 219         excludeTestMaxRange("JVMCIThreads");
 220         excludeTestMaxRange("JVMCIHostThreads");
 221 
 222         /*
 223          * Exclude MallocMaxTestWords as it is expected to exit VM at small values (>=0)
 224          */
 225         excludeTestMinRange("MallocMaxTestWords");
 226 
 227         /*
 228          * Exclude below options as their maximum value would consume too much memory
 229          * and would affect other tests that run in parallel.
 230          */
 231         excludeTestMaxRange("ConcGCThreads");
 232         excludeTestMaxRange("G1ConcRefinementThreads");
 233         excludeTestMaxRange("G1RSetRegionEntries");
 234         excludeTestMaxRange("G1RSetSparseRegionEntries");
 235         excludeTestMaxRange("G1UpdateBufferSize");
 236         excludeTestMaxRange("InitialBootClassLoaderMetaspaceSize");
 237         excludeTestMaxRange("InitialHeapSize");
 238         excludeTestMaxRange("MaxHeapSize");
 239         excludeTestMaxRange("MaxRAM");
 240         excludeTestMaxRange("NewSize");
 241         excludeTestMaxRange("OldSize");
 242         excludeTestMaxRange("ParallelGCThreads");
 243         excludeTestMaxRange("TLABSize");
 244 
 245         /*
 246          * Remove parameters controlling the code cache. As these
 247          * parameters have implications on the physical memory
 248          * reserved by the VM, setting them to large values may hang
 249          * the system and/or may cause concurrently executed tests to
 250          * fail. These parameters are rigorously checked when the code
 251          * cache is initialized (see
 252          * hotspot/src/shared/vm/code/codeCache.cpp), therefore
 253          * omitting testing for them does not pose a problem.
 254          */
 255         excludeTestMaxRange("InitialCodeCacheSize");
 256         excludeTestMaxRange("CodeCacheMinimumUseSpace");

 216         /*
 217          * Exclude JVMCI threads counts from testing similar to other threads counts.
 218          */
 219         excludeTestMaxRange("JVMCIThreads");
 220         excludeTestMaxRange("JVMCIHostThreads");
 221 
 222         /*
 223          * Exclude MallocMaxTestWords as it is expected to exit VM at small values (>=0)
 224          */
 225         excludeTestMinRange("MallocMaxTestWords");
 226 
 227         /*
 228          * Exclude below options as their maximum value would consume too much memory
 229          * and would affect other tests that run in parallel.
 230          */
 231         excludeTestMaxRange("ConcGCThreads");
 232         excludeTestMaxRange("G1ConcRefinementThreads");
 233         excludeTestMaxRange("G1RSetRegionEntries");
 234         excludeTestMaxRange("G1RSetSparseRegionEntries");
 235         excludeTestMaxRange("G1UpdateBufferSize");

 236         excludeTestMaxRange("InitialHeapSize");
 237         excludeTestMaxRange("MaxHeapSize");
 238         excludeTestMaxRange("MaxRAM");
 239         excludeTestMaxRange("NewSize");
 240         excludeTestMaxRange("OldSize");
 241         excludeTestMaxRange("ParallelGCThreads");
 242         excludeTestMaxRange("TLABSize");
 243 
 244         /*
 245          * Remove parameters controlling the code cache. As these
 246          * parameters have implications on the physical memory
 247          * reserved by the VM, setting them to large values may hang
 248          * the system and/or may cause concurrently executed tests to
 249          * fail. These parameters are rigorously checked when the code
 250          * cache is initialized (see
 251          * hotspot/src/shared/vm/code/codeCache.cpp), therefore
 252          * omitting testing for them does not pose a problem.
 253          */
 254         excludeTestMaxRange("InitialCodeCacheSize");
 255         excludeTestMaxRange("CodeCacheMinimumUseSpace");