Home
last modified time | relevance | path

Searched refs:tests (Results 1 – 146 of 146) sorted by relevance

/linux-4.4.14/fs/btrfs/
DMakefile17 btrfs-$(CONFIG_BTRFS_FS_RUN_SANITY_TESTS) += tests/free-space-tests.o \
18 tests/extent-buffer-tests.o tests/btrfs-tests.o \
19 tests/extent-io-tests.o tests/inode-tests.o tests/qgroup-tests.o
DKconfig64 bool "Btrfs will run sanity tests upon loading"
67 This will run some basic sanity tests on the free space cache
69 regression tests and are only really interesting to btrfs
/linux-4.4.14/tools/lib/lockdep/
Drun_tests.sh5 for i in `ls tests/*.c`; do
7 gcc -o tests/$testname -pthread -lpthread $i liblockdep.a -Iinclude -D__USE_LIBLOCKDEP &> /dev/null
9 if [ $(timeout 1 ./tests/$testname | wc -l) -gt 0 ]; then
14 rm tests/$testname
17 for i in `ls tests/*.c`; do
19 gcc -o tests/$testname -pthread -lpthread -Iinclude $i &> /dev/null
21 if [ $(timeout 1 ./lockdep ./tests/$testname | wc -l) -gt 0 ]; then
26 rm tests/$testname
/linux-4.4.14/Documentation/
Dkselftest.txt3 The kernel contains a set of "self tests" under the tools/testing/selftests/
4 directory. These are intended to be small unit tests to exercise individual
7 On some systems, hot-plug tests could hang forever waiting for cpu and
9 to run full range of hot-plug tests. In default mode, hot-plug tests run
14 Running the selftests (hotplug tests are run in limited mode)
17 To build the tests:
21 To run the tests:
24 To build and run the tests with a single command, use:
27 - note that some tests will require root privileges.
33 single test to run, or a list of tests to run.
[all …]
Dhw_random.txt26 fitness tests, and could potentially be bogus (if the
29 a security-conscious person would run fitness tests on the
32 The rng-tools package uses such tests in "rngd", and lets you
DHOWTO225 - the 4.x -next kernel tree for integration tests
320 4.x -next kernel tree for integration tests
Dsvga.txt255 - Hardware testing order slightly changed, tests based on ROM
Dkernel-parameters.txt824 [KNL] verbose self-tests
827 self-tests.
1921 This tests the locking primitive's ability to
2497 no_timer_check [X86,APIC] Disables the code which tests for
3178 callback-flood tests.
3272 wait for five seconds, and so on. This tests RCU's
3318 Run the RCU early boot self tests
3321 Run the RCU bh early boot self tests
3324 Run the RCU sched early boot self tests
Dadding-syscalls.txt462 consider adding tests to the Linux Test Project, or to the xfstests project
Dmemory-barriers.txt790 These two examples are the LB and WWC litmus tests from this paper:
/linux-4.4.14/tools/perf/Documentation/
Dperf-test.txt6 perf-test - Runs sanity tests.
15 This command does assorted sanity tests, initially through linked routines but
16 also will look for a directory with more tests in the form of scripts.
18 To get a list of available tests use 'perf test list', specifying a test name
19 fragment will show all tests that have it.
21 To run just specific tests, inform test name fragments or the numbers obtained
/linux-4.4.14/drivers/net/ethernet/sfc/
Dselftest.c99 static int efx_test_phy_alive(struct efx_nic *efx, struct efx_self_tests *tests) in efx_test_phy_alive() argument
105 tests->phy_alive = rc ? -1 : 1; in efx_test_phy_alive()
111 static int efx_test_nvram(struct efx_nic *efx, struct efx_self_tests *tests) in efx_test_nvram() argument
120 tests->nvram = rc ? -1 : 1; in efx_test_nvram()
134 struct efx_self_tests *tests) in efx_test_interrupts() argument
140 tests->interrupt = -1; in efx_test_interrupts()
162 tests->interrupt = 1; in efx_test_interrupts()
168 struct efx_self_tests *tests) in efx_test_eventq_irq() argument
216 tests->eventq_dma[channel->channel] = dma_seen ? 1 : -1; in efx_test_eventq_irq()
217 tests->eventq_int[channel->channel] = int_seen ? 1 : -1; in efx_test_eventq_irq()
[all …]
Dethtool.c303 struct efx_self_tests *tests, in efx_ethtool_fill_self_tests() argument
310 efx_fill_test(n++, strings, data, &tests->phy_alive, in efx_ethtool_fill_self_tests()
312 efx_fill_test(n++, strings, data, &tests->nvram, in efx_ethtool_fill_self_tests()
314 efx_fill_test(n++, strings, data, &tests->interrupt, in efx_ethtool_fill_self_tests()
320 &tests->eventq_dma[channel->channel], in efx_ethtool_fill_self_tests()
324 &tests->eventq_int[channel->channel], in efx_ethtool_fill_self_tests()
329 efx_fill_test(n++, strings, data, &tests->memory, in efx_ethtool_fill_self_tests()
331 efx_fill_test(n++, strings, data, &tests->registers, in efx_ethtool_fill_self_tests()
345 efx_fill_test(n++, strings, data, &tests->phy_ext[i], in efx_ethtool_fill_self_tests()
355 &tests->loopback[mode], mode, n, in efx_ethtool_fill_self_tests()
Dselftest.h49 int efx_selftest(struct efx_nic *efx, struct efx_self_tests *tests,
Dsiena.c95 static int siena_test_chip(struct efx_nic *efx, struct efx_self_tests *tests) in siena_test_chip() argument
109 tests->registers = in siena_test_chip()
Dnet_driver.h1256 int (*test_chip)(struct efx_nic *efx, struct efx_self_tests *tests);
Dfalcon.c1894 falcon_b0_test_chip(struct efx_nic *efx, struct efx_self_tests *tests) in falcon_b0_test_chip() argument
1913 tests->registers = in falcon_b0_test_chip()
Def10.c4392 efx_ef10_test_chip(struct efx_nic *efx, struct efx_self_tests *tests) in efx_ef10_test_chip() argument
4403 tests->memory = efx_ef10_run_bist(efx, MC_CMD_MC_MEM_BIST) ? -1 : 1; in efx_ef10_test_chip()
4404 tests->registers = efx_ef10_run_bist(efx, MC_CMD_REG_BIST) ? -1 : 1; in efx_ef10_test_chip()
/linux-4.4.14/crypto/async_tx/
Draid6test.c155 static int test(int disks, int *tests) in test() argument
187 (*tests)++; in test()
198 int tests = 0; in raid6_test() local
212 err += test(4, &tests); in raid6_test()
214 err += test(5, &tests); in raid6_test()
219 err += test(11, &tests); in raid6_test()
220 err += test(12, &tests); in raid6_test()
228 err += test(24, &tests); in raid6_test()
230 err += test(NDISKS, &tests); in raid6_test()
234 tests, err, err == 1 ? "" : "s"); in raid6_test()
/linux-4.4.14/drivers/of/unittest-data/
Dtestcases.dts12 #include "tests-phandle.dtsi"
13 #include "tests-interrupts.dtsi"
14 #include "tests-match.dtsi"
15 #include "tests-platform.dtsi"
16 #include "tests-overlay.dtsi"
28 phandle-tests {
Dtests-platform.dtsi4 platform-tests {
Dtests-phandle.dtsi11 phandle-tests {
/linux-4.4.14/tools/perf/tests/
DBuild38 $(OUTPUT)tests/llvm-src-base.c: tests/bpf-script-example.c
40 $(Q)echo '#include <tests/llvm.h>' > $@
45 $(OUTPUT)tests/llvm-src-kbuild.c: tests/bpf-script-test-kbuild.c
47 $(Q)echo '#include <tests/llvm.h>' > $@
Dmake5 @echo "Testing Makefile"; $(MAKE) -sf tests/make MK=Makefile
6 @echo "Testing Makefile.perf"; $(MAKE) -sf tests/make MK=Makefile.perf
10 @echo "Testing Makefile"; $(MAKE) -sf tests/make MK=Makefile $@
17 # FIXME looks like x86 is the only arch running tests ;-)
72 # $(run) contains all available tests
124 # $(run_O) contains same portion of $(run) tests with '_O' attached
125 # to distinguish O=... tests
128 # disable some tests for O=...
260 @cmd="$(PERF)/tests/perf-targz-src-pkg $(PERF)"; \
Dbuiltin-test.c177 static struct test *tests[] = { variable
237 for (j = 0; j < ARRAY_SIZE(tests); j++) \
238 for (t = &tests[j][0]; t->func; t++)
Dparse-events.c1772 #define TEST_EVENTS(tests) \ in test__parse_events() argument
1774 ret1 = test_events(tests, ARRAY_SIZE(tests)); \ in test__parse_events()
/linux-4.4.14/tools/testing/selftests/net/
Dsocket.c25 static struct socket_testcase tests[] = { variable
43 for (i = 0; i < ARRAY_SIZE(tests); i++) { in run_tests()
44 struct socket_testcase *s = &tests[i]; in run_tests()
/linux-4.4.14/tools/perf/tests/attr/
DREADME1 The struct perf_event_attr test (attr tests) support
12 The attr tests consist of following parts:
14 tests/attr.c
25 tests/attr.py
30 tests/attr/
33 Following tests are defined (with perf commands):
/linux-4.4.14/tools/testing/selftests/ftrace/
DREADME31 * Take care with side effects as the tests are run with root privilege.
33 * The tests should not run for a long period of time (more than 1 min.)
34 These are to be unit tests.
41 * Note that the tests are run with "set -e" (errexit) option. If any
44 * The tests can return some result codes instead of pass or fail by
/linux-4.4.14/Documentation/isdn/
DHiSax.cert23 Additional ITU approval tests have been carried out for all generic cards
26 These tests included all layers 1-3 and as well all functional tests for
29 regarded as approved for those tests. Some additional electrical tests
32 solution has been tested including those electrical tests. So if cards
34 for those electrical tests is valid for linux, too.
DREADME.x25170 tests, the x25-utils package contains a modified version of telnet
172 use those for your first tests. Furthermore, you might check
/linux-4.4.14/tools/testing/selftests/futex/
DREADME6 Functional tests shall test the documented behavior of the futex operation
8 odd corner cases, regression tests, and abject abuse and misuse.
24 the individual tests on mailing list discussions and bug reports.
53 o FIXME: decide on a sane test naming scheme. Currently the tests are named
55 problem as we intend to write multiple tests which collide in this namespace.
/linux-4.4.14/Documentation/networking/mac80211_hwsim/
DREADME23 and always reproduce the same setup for future tests. In addition,
25 tests regardless of regulatory rules.
30 point and a station) or large scale tests (multiple access points with
67 git://w1.fi/srv/git/hostap.git and mac80211_hwsim/tests subdirectory
68 (http://w1.fi/gitweb/gitweb.cgi?p=hostap.git;a=tree;f=mac80211_hwsim/tests)
/linux-4.4.14/Documentation/power/
Ddrivers-testing.txt38 2). [As far as the STR tests are concerned, it should not matter whether or
44 Each of the above tests should be repeated several times and the STD tests
45 should be mixed with the STR tests. If any of them fails, the driver cannot be
Dbasic-pm-debugging.txt89 contains a space-separated list of all available tests (including "none" that
94 one and the "core" level tests the hardware and drivers as deeply as possible
143 A failure of any of the "platform", "processors" or "core" tests may cause your
/linux-4.4.14/arch/m68k/ifpsp060/
DTEST.DOC32 The files itest.sa and ftest.sa contain simple tests to check
38 hexadecimal images of the actual tests. This format is the
85 are individual tests, they each require their own "Call-out" sections.
148 3 different calls to the package if each of the three following tests
151 main fp test: tests (1) unimp effective address exception
155 FP unimplemented: tests FP unimplemented exception. this one is
156 separate from the previous tests for systems that don't
159 FP enabled: tests enabled snan/operr/ovfl/unfl/dz/inex.
171 Again, itest.sa and ftest.sa are simple tests and do not thoroughly
DMISC198 tests
/linux-4.4.14/samples/bpf/
Dtest_verifier.c42 static struct bpf_test tests[] = { variable
1225 for (i = 0; i < ARRAY_SIZE(tests); i++) { in test()
1226 struct bpf_insn *prog = tests[i].insns; in test()
1227 int prog_type = tests[i].prog_type; in test()
1229 int *fixup = tests[i].fixup; in test()
1230 int *prog_array_fixup = tests[i].prog_array_fixup; in test()
1251 printf("#%d %s ", i, tests[i].descr); in test()
1257 if (unpriv && tests[i].result_unpriv != UNDEF) in test()
1258 expected_result = tests[i].result_unpriv; in test()
1260 expected_result = tests[i].result; in test()
[all …]
/linux-4.4.14/net/hsr/
DKconfig21 described in IEC 62439-3:2010 (HSRv0), but no compliancy tests have
24 You need to perform any and all necessary tests yourself before
/linux-4.4.14/Documentation/arm/VFP/
Drelease-notes.txt31 All the above pass softfloat tests with the following exceptions:
39 Other operations which have been tested by basic assembly-only tests
/linux-4.4.14/tools/perf/
DMakefile.perf350 tests/%.o: $(OUTPUT)tests/%.o
559 install-tests: all install-gtk
560 $(call QUIET_INSTALL, tests) \
562 $(INSTALL) tests/attr.py '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/tests'; \
564 $(INSTALL) tests/attr/* '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/tests/attr'
566 install-bin: install-tools install-tests
DMakefile81 @$(MAKE) SHUF=1 -f tests/make --no-print-directory
DBuild27 perf-y += tests/
/linux-4.4.14/lib/
DKconfig.kgdb40 the tests. The most basic of this I/O module is to boot
44 bool "KGDB: Run tests on boot"
48 Run the kgdb tests on boot up automatically without the need
52 string "KGDB: which internal kgdb tests to run"
Dtest_bpf.c437 static struct bpf_test tests[] = { variable
5214 if (tests[which].fill_helper) in filter_length()
5215 return tests[which].u.ptr.len; in filter_length()
5217 fp = tests[which].u.insns; in filter_length()
5227 if (tests[which].fill_helper) in filter_pointer()
5228 return tests[which].u.ptr.insns; in filter_pointer()
5230 return tests[which].u.insns; in filter_pointer()
5235 __u8 test_type = tests[which].aux & TEST_TYPE_MASK; in generate_filter()
5247 if (tests[which].aux & FLAG_EXPECTED_FAIL) { in generate_filter()
5293 __u8 test_type = tests[which].aux & TEST_TYPE_MASK; in release_filter()
[all …]
DKconfig.debug1068 bool "Locking API boot-time self-tests"
1079 tristate "torture tests for locking"
1084 This option provides a kernel module that runs torture tests
1088 Say Y here if you want kernel locking-primitive torture tests
1090 Say M if you want these torture tests to build as a module.
1241 tristate "torture tests for RCU"
1248 This option provides a kernel module that runs torture tests
1252 Say Y here if you want RCU torture tests to be built into
1254 Say M if you want the RCU torture tests to build as a module.
1258 bool "torture tests for RCU runnable by default"
[all …]
/linux-4.4.14/tools/perf/arch/arm/
DBuild2 libperf-$(CONFIG_DWARF_UNWIND) += tests/
/linux-4.4.14/tools/perf/arch/x86/
DBuild2 libperf-y += tests/
/linux-4.4.14/tools/perf/arch/arm64/
DBuild2 libperf-$(CONFIG_DWARF_UNWIND) += tests/
/linux-4.4.14/drivers/gpu/drm/nouveau/
DKbuild8 #- code also used by various userspace tools/tests
13 #- code also used by various userspace tools/tests
/linux-4.4.14/Documentation/devicetree/
Dof_unittest.txt26 the test data required for executing the unit tests automated in
30 drivers/of/unittest-data/tests-interrupts.dtsi
31 drivers/of/unittest-data/tests-platform.dtsi
32 drivers/of/unittest-data/tests-phandle.dtsi
33 drivers/of/unittest-data/tests-match.dtsi
/linux-4.4.14/tools/perf/arch/x86/tests/
DBuild4 libperf-y += arch-tests.o
/linux-4.4.14/include/uapi/linux/netfilter/
Dxt_u32.h37 struct xt_u32_test tests[XT_U32_MAXSIZE+1]; member
/linux-4.4.14/tools/testing/ktest/examples/
Dtest.conf59 INCLUDE include/tests.conf
Dkvm.conf90 INCLUDE include/tests.conf
DREADME11 lots of different architectures. It only does build tests, but makes
/linux-4.4.14/tools/testing/selftests/vm/
DMakefile8 BINARIES += mlock2-tests
Drun_vmtests136 ./mlock2-tests
/linux-4.4.14/drivers/mmc/card/
DKconfig65 in host controllers. The tests are executed by writing to the
67 on your card will be overwritten by these tests.
/linux-4.4.14/Documentation/fault-injection/
Dnotifier-error-inject.txt98 These scripts first do simple online and offline tests and then do fault
99 injection tests if notifier error injection module is available.
Dfault-injection.txt53 should_fail() that pass all the other tests.
/linux-4.4.14/arch/x86/math-emu/
DREADME170 Timing: Some simple timing tests have been made on the emulator functions.
172 measured on a 33MHz 386 with 64k cache. The Turbo C tests were under
264 The emulator passes the "paranoia" tests (compiled with gcc 2.3.3 or
268 properly performing FPU cannot pass the 'paranoia' tests for 'double'
326 instr arg range # tests 63.7 63.8 63.9 worst at arg
340 486DX2/66 (other tests indicate that an Intel 486DX produces
341 identical results). The tests were basically the same as those used
343 the same). The total number of tests for each instruction are given
344 at the end of the table, in case each about 100k tests were performed.
/linux-4.4.14/drivers/mtd/
DMakefile33 obj-y += chips/ lpddr/ maps/ devices/ nand/ onenand/ tests/
DKconfig16 tristate "MTD tests support (DANGEROUS)"
19 This option includes various MTD tests into compilation. The tests
23 WARNING: some of the tests will ERASE entire MTD device which they
24 test. Do not use these tests unless you really know what you do.
/linux-4.4.14/arch/arm/mach-u300/
DKconfig39 SPI device to be used for loopback tests. Regularly used
/linux-4.4.14/drivers/staging/media/mn88473/
DTODO14 checkpatch.pl tests. I don't want waste my time to review this kind of
/linux-4.4.14/drivers/staging/media/mn88472/
DTODO14 checkpatch.pl tests. I don't want waste my time to review this kind of
/linux-4.4.14/tools/testing/selftests/zram/
DREADME25 Two functional tests: zram01 and zram02:
/linux-4.4.14/scripts/coccinelle/null/
Deno.cocci40 cocci.print_secs("IS_ERR that should be NULL tests",p2)
/linux-4.4.14/net/netfilter/
Dxt_u32.c34 ct = &data->tests[testind]; in u32_match_it()
/linux-4.4.14/Documentation/dmaengine/
Ddmatest.txt49 before returning. For example, the following scripts wait for 42 tests
85 number of tests executed, number that failed, and a result code.
/linux-4.4.14/Documentation/scsi/
Dqlogicfas.txt62 you can do multiple tests on smaller files. Then do a COMP to verify
64 tests, otherwise you will test your RAM and not the files). Then do
Dosd.txt57 osd_test.c User-mode application to call the kernel tests
174 TODO: More user-mode control on tests.
Din2000.txt138 to see what happens: my tests showed little difference either way.
DChangeLog.lpfc1278 * Fixed crash on driver rmmod after error injection tests and
1793 * Use lpfc_is_LC_HBA() macro that tests pcidev->device directly
DChangeLog.1992-19971739 * aha1542.c: Replace 16 with sizeof(SCpnt->sense_buffer). Add tests
/linux-4.4.14/Documentation/virtual/kvm/
Dreview-checklist.txt20 7. Emulator changes should be accompanied by unit tests for qemu-kvm.git
/linux-4.4.14/Documentation/RCU/
Dtorture.txt16 result in the tests being loaded into the base kernel. In this case,
18 whether the RCU torture tests are to be started immediately during
21 restart the tests, regardless of the initial state specified by the
24 You will normally -not- want to start the RCU torture tests during boot
177 "rcu_busted": This tests an intentionally incorrect version
Dtrace.txt32 The first line shows the number of rcutorture tests that have completed
/linux-4.4.14/drivers/staging/media/davinci_vpfe/
DTODO21 layer and compatibility tests that warrants (using the libv4l's LD_PRELOAD
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-bus-usb-lvstest2 Speed Link Layer tests. These nodes are available in sysfs only when lvs
/linux-4.4.14/Documentation/locking/
Dlocktorture.txt6 that runs torture tests on core kernel locking primitives. The kernel
8 kernel to be tested, if desired. The tests periodically output status
/linux-4.4.14/arch/arm/probes/kprobes/
Dtest-thumb.c21 #define DONT_TEST_IN_ITBLOCK(tests) \ argument
23 tests \
26 #define CONDITION_INSTRUCTIONS(cc_pos, tests) \ argument
28 DONT_TEST_IN_ITBLOCK(tests) \
Dtest-core.c1605 static int run_test_cases(void (*tests)(void), const union decode_item *table) in run_test_cases()
1619 tests(); in run_test_cases()
/linux-4.4.14/scripts/coccinelle/misc/
Dboolinit.cocci1 /// Bool initializations should use true and false. Bool tests don't need
/linux-4.4.14/arch/xtensa/lib/
Dmemset.S53 movi a6, 3 # for alignment tests
/linux-4.4.14/drivers/of/
DKconfig15 bool "Device Tree runtime unit tests"
/linux-4.4.14/scripts/coccinelle/iterators/
Duse_after_iter.cocci6 //#reported reference is at the label of this goto. Some flag tests
/linux-4.4.14/tools/usb/usbip/
DINSTALL29 the results of its tests to speed up reconfiguring. Caching is
55 3. Optionally, type `make check' to run any self-tests that come with
216 Enable the cache: use and save the results of the tests in FILE,
/linux-4.4.14/Documentation/networking/
Ddriver.txt47 For a non-scatter-gather supporting card, the three tests simply become:
De1000e.txt279 NOTE: When validating enable/disable tests on some parts (82578, for example)
280 you need to add a few seconds between tests when working with ethtool.
Dde4x5.txt87 pause whilst the driver figures out where its media went). My tests
Dcs89x0.txt392 To run the diagnostics tests on the CS8900/20 adapter:
408 assigned during hardware configuration. The following tests are performed:
Deql.txt335 Subject: EQL driver tests
Ddecnet.txt173 - How far though the above set of tests can you get ?
Dvortex.txt446 asks more questions, asks for more tests, asks for patches to be
Dixgb.txt214 # several network benchmark tests, your mileage may vary
Dscaling.txt95 initial tests, so limit the number of queues to the number of CPU cores
/linux-4.4.14/Documentation/usb/
Dmtouchusb.txt14 Performed multiple successful tests with an EXII-5010UC
/linux-4.4.14/arch/powerpc/
DKconfig.debug67 bool "Run self-tests of the code-patching code."
72 bool "Run self-tests of the feature-fixup code."
77 bool "Run self-tests of the MSI bitmap code."
/linux-4.4.14/net/bluetooth/
DKconfig76 Run self tests when initializing the Bluetooth subsystem. This
/linux-4.4.14/tools/perf/bench/
Dnuma.c1674 static const char *tests[][MAX_ARGS] = { variable
1749 int nr = ARRAY_SIZE(tests); in bench_all()
1757 run_bench_numa(tests[i][0], tests[i] + 1); in bench_all()
/linux-4.4.14/arch/blackfin/
DKconfig.debug235 bool "isram boot self tests"
238 Run some self tests of the isram driver code at boot.
/linux-4.4.14/Documentation/timers/
Dhrtimers.txt153 timer tests in order to ensure specification compliance. We also ran
154 tests on low-resolution clocks.
/linux-4.4.14/arch/mn10300/
DKconfig.debug15 bool "Run tests on the misalignment handler"
/linux-4.4.14/Documentation/infiniband/
Dipoib.txt96 performance, because it adds tests to the fast path.
/linux-4.4.14/Documentation/cpu-freq/
Dboost.txt40 to do tests with and without boosting.
/linux-4.4.14/tools/build/Documentation/
DBuild.txt98 You can check the 'ex' example in 'tools/build/tests/ex' for more details.
/linux-4.4.14/Documentation/i2c/
Dfunctionality94 Before a client tries to attach to an adapter, or even do tests to check
/linux-4.4.14/Documentation/power/regulator/
Doverview.txt124 If the regulator request passes all the constraint tests
/linux-4.4.14/arch/x86/
DKconfig.debug317 Do change_page_attr() self-tests every 30 seconds.
363 Some simple tests are run to verify IMR bounds checking, alignment
/linux-4.4.14/kernel/trace/
DKconfig501 This option performs a series of startup tests on ftrace. On bootup
502 a series of tests are made to verify that the tracer is
503 functioning properly. It will do tests on all the configured
/linux-4.4.14/arch/m68k/fpsp040/
Dx_operr.S302 | End_operr tests for operr enabled. If not, it cleans up the stack
/linux-4.4.14/drivers/cpufreq/
DKconfig.arm166 tests but not documented in any datasheet.
/linux-4.4.14/arch/mips/
DKconfig.debug110 bool "Enable spinlock timing tests in debugfs"
/linux-4.4.14/Documentation/vm/
Dhwpoison.txt171 Test suite (hwpoison specific portable tests in tsrc)
Dhugetlbpage.txt339 The most complete set of hugetlb tests are in the libhugetlbfs repository.
342 functionality, please add appropriate tests to libhugetlbfs.
Dslub.txt106 In that case slabinfo -v simply tests all reachable objects. Usually
/linux-4.4.14/Documentation/hwmon/
Dw83792d117   - The function of chassis open detection needs more tests.
/linux-4.4.14/Documentation/filesystems/
Dvfat.txt212 This tests quite a few parts of the vfat filesystem and additional
213 tests for new features or untested features would be appreciated.
/linux-4.4.14/Documentation/fb/
Dudlfb.txt155 performance tests to start and finish in a very short
Dmatroxfb.txt307 pretty effects on screen. Device was not destroyed during tests. :-)
/linux-4.4.14/Documentation/cgroups/
Dmemcg_test.txt180 Use tests like the following.
/linux-4.4.14/
DREPORTING-BUGS139 bug reports. That may include running new tests, applying patches,
DCREDITS1109 D: Mitsumi LU005 tests and fixes
/linux-4.4.14/fs/affs/
DChanges201 I not find this during my tests?
/linux-4.4.14/Documentation/x86/
Dexception-tables.txt18 tests, this normally unneeded verification used up a considerable
/linux-4.4.14/drivers/iommu/
DKconfig37 Enable self-tests for LPAE page table allocator. This performs
/linux-4.4.14/scripts/
DKbuild.include82 # output directory for tests below
/linux-4.4.14/arch/m68k/
DKconfig.cpu326 math coprocessor. This makes the kernel a bit faster as no tests
/linux-4.4.14/Documentation/scheduler/
Dsched-deadline.txt242 More complex schedulability tests for global EDF have been developed in
251 about schedulability tests for multi-processor real-time scheduling can be
/linux-4.4.14/Documentation/serial/
Ddriver75 This function tests whether the transmitter fifo and shifter
/linux-4.4.14/drivers/usb/gadget/
DKconfig360 and its driver through a basic set of functional tests.
/linux-4.4.14/drivers/usb/gadget/legacy/
DKconfig32 and its driver through a basic set of functional tests.
/linux-4.4.14/crypto/
DKconfig137 bool "Disable run-time self tests"
141 Disable run-time self tests that normally take place at
/linux-4.4.14/arch/alpha/
DKconfig510 elimiate as many runtime tests as possible.
/linux-4.4.14/drivers/usb/host/
DKconfig783 to include other tests that require support from a HCD driver.
/linux-4.4.14/arch/m68k/ifpsp060/src/
Dfpsp.S16328 # IEEE Nonaware tests #
16330 # For the IEEE nonaware tests, only the false branch changes the #
16586 # Miscellaneous tests #
16588 # For the IEEE miscellaneous tests, all but fdbf and fdbt can set bsun. #
16683 # IEEE Aware tests #
16685 # For the IEEE aware tests, action is only taken if the result is false.#
16688 # The BSUN exception will not be set for any of these tests. #
/linux-4.4.14/drivers/ide/
DKconfig363 onboard chipsets. It also tests for Simplex mode and enables
/linux-4.4.14/arch/arm/
DKconfig.debug1625 Perform tests of kprobes API and instruction set simulation.
/linux-4.4.14/Documentation/kbuild/
Dmakefiles.txt534 cc-ifversion tests the version of $(CC) and equals the fourth parameter
/linux-4.4.14/Documentation/filesystems/cifs/
DCHANGES979 clients. basic posix file i/o tests now work on big endian machines, not just le
/linux-4.4.14/Documentation/video4linux/
Dvivid.txt238 all tests that v4l2-compliance is doing will fail afterwards.
/linux-4.4.14/Documentation/cdrom/
Dcdrom-standard.tex728 set, that it contains tracks of type `data mode 1.' Only if all tests
/linux-4.4.14/Documentation/block/
Dbiodoc.txt284 capabilities for certain kinds of fitness tests. Having direct interfaces at
/linux-4.4.14/Documentation/trace/
Dftrace.txt905 when performing latency tests.