# # This is an example of various tests that you can run # # The variable TEST can be of boot, build, randconfig, or test. # # Note that TEST is a variable created with ':=' and only exists # throughout the config processing (not during the tests itself). # # The TEST option (defined with '=') is used to tell ktest.pl # what test to run after a successful boot. The TEST option is # persistent into the test runs. # # The config that includes this file may define a BOOT_TYPE # variable that tells this config what type of boot test to run. # If it's not defined, the below DEFAULTS will set the default # to 'oldconfig'. # DEFAULTS IF NOT DEFINED BOOT_TYPE BOOT_TYPE := oldconfig # The config that includes this file may define a RUN_TEST # variable that will tell this config what test to run. # (what to set the TEST option to). # DEFAULTS IF NOT DEFINED RUN_TEST # Requires that hackbench is in the PATH RUN_TEST := ${SSH} hackbench 50 # If TEST is set to 'boot' then just build a kernel and boot # the target. TEST_START IF ${TEST} == boot TEST_TYPE = boot # Notice how we set the BUILD_TYPE option to the BOOT_TYPE variable. BUILD_TYPE = ${BOOT_TYPE} # Do not do a make mrproper. BUILD_NOCLEAN = 1 # If you only want to build the kernel, and perhaps install # and test it yourself, then just set TEST to build. TEST_START IF ${TEST} == build TEST_TYPE = build BUILD_TYPE = ${BOOT_TYPE} BUILD_NOCLEAN = 1 # Build, install, boot and test with a randconfg 10 times. # It is important that you have set MIN_CONFIG in the config # that includes this file otherwise it is likely that the # randconfig will not have the necessary configs needed to # boot your box. This version of the test requires a min # config that has enough to make sure the target has network # working. TEST_START ITERATE 10 IF ${TEST} == randconfig MIN_CONFIG = ${CONFIG_DIR}/config-min-net TEST_TYPE = test BUILD_TYPE = randconfig TEST = ${RUN_TEST} # This is the same as above, but only tests to a boot prompt. # The MIN_CONFIG used here does not need to have networking # working. TEST_START ITERATE 10 IF ${TEST} == randconfig && ${MULTI} TEST_TYPE = boot BUILD_TYPE = randconfig MIN_CONFIG = ${CONFIG_DIR}/config-min MAKE_CMD = make # This builds, installs, boots and tests the target. TEST_START IF ${TEST} == test TEST_TYPE = test BUILD_TYPE = ${BOOT_TYPE} TEST = ${RUN_TEST} BUILD_NOCLEAN = 1 idden' name='h' value='nds-private-remove'/>
path: root/tools/perf/bench
diff options
context:
space:
mode:
authorBjorn Helgaas <bhelgaas@google.com>2016-12-28 14:55:16 -0600
committerBjorn Helgaas <bhelgaas@google.com>2017-01-11 09:11:15 -0600
commit89e9f7bcd8744ea25fcf0ac671b8d72c10d7d790 (patch)
treee941c52704b59bc7d5ffe0bbaa2d42b8fec8976a /tools/perf/bench
parenta782b5f986c3fa1cfa7f2b57941200c6a5809242 (diff)
x86/PCI: Ignore _CRS on Supermicro X8DTH-i/6/iF/6F
Martin reported that the Supermicro X8DTH-i/6/iF/6F advertises incorrect host bridge windows via _CRS: pci_root PNP0A08:00: host bridge window [io 0xf000-0xffff] pci_root PNP0A08:01: host bridge window [io 0xf000-0xffff] Both bridges advertise the 0xf000-0xffff window, which cannot be correct. Work around this by ignoring _CRS on this system. The downside is that we may not assign resources correctly to hot-added PCI devices (if they are possible on this system). Link: https://bugzilla.kernel.org/show_bug.cgi?id=42606 Reported-by: Martin Burnicki <martin.burnicki@meinberg.de> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com> CC: stable@vger.kernel.org
Diffstat (limited to 'tools/perf/bench')