0001 #
0002 # This file has some examples for creating a MIN_CONFIG.
0003 # (A .config file that is the minimum for a machine to boot, or
0004 # to boot and make a network connection.)
0005 #
0006 # A MIN_CONFIG is very useful as it is the minimum configuration
0007 # needed to boot a given machine. You can debug someone else's
0008 # .config by only setting the configs in your MIN_CONFIG. The closer
0009 # your MIN_CONFIG is to the true minimum set of configs needed to
0010 # boot your machine, the closer the config you test with will be
0011 # to the users config that had the failure.
0012 #
0013 # The make_min_config test allows you to create a MIN_CONFIG that
0014 # is truly the minimum set of configs needed to boot a box.
0015 #
0016 # In this example, the final config will reside in
0017 # ${CONFIG_DIR}/config-new-min and ${CONFIG_DIR}/config-new-min-net.
0018 # Just move one to the location you have set for MIN_CONFIG.
0019 #
0020 # The first test creates a MIN_CONFIG that will be the minimum
0021 # configuration to boot ${MACHINE} and be able to ssh to it.
0022 #
0023 # The second test creates a MIN_CONFIG that will only boot
0024 # the target and most likely will not let you ssh to it. (Notice
0025 # how the second test uses the first test's result to continue with.
0026 # This is because the second test config is a subset of the first).
0027 #
0028 # The ${CONFIG_DIR}/config-skip (and -net) will hold the configs
0029 # that ktest.pl found would not boot the target without them set.
0030 # The config-new-min holds configs that ktest.pl could not test
0031 # directly because another config that was needed to boot the box
0032 # selected them. Sometimes it is possible that this file will hold
0033 # the true minimum configuration. You can test to see if this is
0034 # the case by running the boot test with BOOT_TYPE = allnoconfig and
0035 # setting setting the MIN_CONFIG to ${CONFIG_DIR}/config-skip. If the
0036 # machine still boots, then you can use the config-skip as your MIN_CONFIG.
0037 #
0038 # These tests can run for several hours (and perhaps days).
0039 # It's OK to kill the test with a Ctrl^C. By restarting without
0040 # modifying this config, ktest.pl will notice that the config-new-min(-net)
0041 # exists, and will use that instead as the starting point.
0042 # The USE_OUTPUT_MIN_CONFIG is set to 1 to keep ktest.pl from asking
0043 # you if you want to use the OUTPUT_MIN_CONFIG as the starting point.
0044 # By using the OUTPUT_MIN_CONFIG as the starting point will allow ktest.pl to
0045 # start almost where it left off.
0046 #
0047 TEST_START IF ${TEST} == min-config
0048 TEST_TYPE = make_min_config
0049 OUTPUT_MIN_CONFIG = ${CONFIG_DIR}/config-new-min-net
0050 IGNORE_CONFIG = ${CONFIG_DIR}/config-skip-net
0051 MIN_CONFIG_TYPE = test
0052 TEST = ${SSH} echo hi
0053 USE_OUTPUT_MIN_CONFIG = 1
0054
0055 TEST_START IF ${TEST} == min-config && ${MULTI}
0056 TEST_TYPE = make_min_config
0057 OUTPUT_MIN_CONFIG = ${CONFIG_DIR}/config-new-min
0058 IGNORE_CONFIG = ${CONFIG_DIR}/config-skip
0059 MIN_CONFIG = ${CONFIG_DIR}/config-new-min-net
0060 USE_OUTPUT_MIN_CONFIG = 1
