1# 2# This file has some examples for creating a MIN_CONFIG. 3# (A .config file that is the minimum for a machine to boot, or 4# to boot and make a network connection.) 5# 6# A MIN_CONFIG is very useful as it is the minimum configuration 7# needed to boot a given machine. You can debug someone else's 8# .config by only setting the configs in your MIN_CONFIG. The closer 9# your MIN_CONFIG is to the true minimum set of configs needed to 10# boot your machine, the closer the config you test with will be 11# to the users config that had the failure. 12# 13# The make_min_config test allows you to create a MIN_CONFIG that 14# is truly the minimum set of configs needed to boot a box. 15# 16# In this example, the final config will reside in 17# ${CONFIG_DIR}/config-new-min and ${CONFIG_DIR}/config-new-min-net. 18# Just move one to the location you have set for MIN_CONFIG. 19# 20# The first test creates a MIN_CONFIG that will be the minimum 21# configuration to boot ${MACHINE} and be able to ssh to it. 22# 23# The second test creates a MIN_CONFIG that will only boot 24# the target and most likely will not let you ssh to it. (Notice 25# how the second test uses the first test's result to continue with. 26# This is because the second test config is a subset of the first). 27# 28# The ${CONFIG_DIR}/config-skip (and -net) will hold the configs 29# that ktest.pl found would not boot the target without them set. 30# The config-new-min holds configs that ktest.pl could not test 31# directly because another config that was needed to boot the box 32# selected them. Sometimes it is possible that this file will hold 33# the true minimum configuration. You can test to see if this is 34# the case by running the boot test with BOOT_TYPE = allnoconfig and 35# setting setting the MIN_CONFIG to ${CONFIG_DIR}/config-skip. If the 36# machine still boots, then you can use the config-skip as your MIN_CONFIG. 37# 38# These tests can run for several hours (and perhaps days). 39# It's OK to kill the test with a Ctrl^C. By restarting without 40# modifying this config, ktest.pl will notice that the config-new-min(-net) 41# exists, and will use that instead as the starting point. 42# The USE_OUTPUT_MIN_CONFIG is set to 1 to keep ktest.pl from asking 43# you if you want to use the OUTPUT_MIN_CONFIG as the starting point. 44# By using the OUTPUT_MIN_CONFIG as the starting point will allow ktest.pl to 45# start almost where it left off. 46# 47TEST_START IF ${TEST} == min-config 48TEST_TYPE = make_min_config 49OUTPUT_MIN_CONFIG = ${CONFIG_DIR}/config-new-min-net 50IGNORE_CONFIG = ${CONFIG_DIR}/config-skip-net 51MIN_CONFIG_TYPE = test 52TEST = ${SSH} echo hi 53USE_OUTPUT_MIN_CONFIG = 1 54 55TEST_START IF ${TEST} == min-config && ${MULTI} 56TEST_TYPE = make_min_config 57OUTPUT_MIN_CONFIG = ${CONFIG_DIR}/config-new-min 58IGNORE_CONFIG = ${CONFIG_DIR}/config-skip 59MIN_CONFIG = ${CONFIG_DIR}/config-new-min-net 60USE_OUTPUT_MIN_CONFIG = 1 61