Home
last modified time | relevance | path

Searched refs:testing (Results 1 – 200 of 273) sorted by relevance

12

/linux-4.1.27/Documentation/
Dkselftest.txt3 The kernel contains a set of "self tests" under the tools/testing/selftests/
18 $ make -C tools/testing/selftests
22 $ make -C tools/testing/selftests run_tests
36 $ make -C tools/testing/selftests TARGETS=ptrace run_tests
41 See the top-level tools/testing/selftests/Makefile for the list of all
49 $ make -C tools/testing/selftests hotplug
52 $ make -C tools/testing/selftests run_hotplug
Dxz.txt30 The xz_dec_test module is for testing xz_dec. xz_dec_test is not
104 it is good to know this if testing the code e.g. with the test files
DSubmittingDrivers99 anything. For the driver testing instructions see
100 Documentation/power/drivers-testing.txt and for a relatively
Dapplying-patches.txt223 ftp://ftp.kernel.org/pub/linux/kernel/v2.6/testing/
308 tool) tree to be in a reasonably sane state adequate for testing.
316 This is a good branch to run for people who want to help out testing
398 sometimes even without prior testing in -mm).
401 ensure maximum testing.
448 I hope you are now clear on how to apply the various patches and help testing
DIntel-IOMMU.txt109 - For compatibility testing, could use unity map domain for all devices, just
Dhw_random.txt90 did the "brains" and all the testing.
DSubmitChecklist40 combinations. This is very hard to get right with testing -- brainpower
Dbcache.txt193 Solution: warm the cache by doing writes, or use the testing branch (there's
424 artificially reduce the size of the cache at runtime. Mostly for testing
425 purposes (i.e. testing how different size caches affect your hit rate), but
Dstable_kernel_rules.txt64 git tree (for instance, because it deserves more regression testing first).
Dsvga.txt255 - Hardware testing order slightly changed, tests based on ROM
271 - Direct testing of SVGA adapters turned off by default, `scan'
Dgcov.txt18 gcov profiling kernel support enables the use of GCC's coverage testing
DHOWTO249 be in a reasonably sane state adequate for testing. The goal is to
324 testing repository exists into which virtually all subsystem trees are
576 - testing results
Dkmemleak.txt113 you can find new unreferenced objects; this should help with testing
Drtc.txt207 If all else fails, check out the tools/testing/selftests/timers/rtctest.c test!
/linux-4.1.27/Documentation/fault-injection/
Dfault-injection.txt246 tools/testing/fault-injection/failcmd.sh. Please run a command
247 "./tools/testing/fault-injection/failcmd.sh --help" for more information and
252 Run a command "make -C tools/testing/selftests/ run_tests" with injecting slab
255 # ./tools/testing/fault-injection/failcmd.sh \
256 -- make -C tools/testing/selftests/ run_tests
261 # ./tools/testing/fault-injection/failcmd.sh --times=100 \
262 -- make -C tools/testing/selftests/ run_tests
268 ./tools/testing/fault-injection/failcmd.sh --times=100 \
269 -- make -C tools/testing/selftests/ run_tests
Dnotifier-error-inject.txt92 There are tools/testing/selftests using the notifier error injection features
95 * tools/testing/selftests/cpu-hotplug/on-off-test.sh
96 * tools/testing/selftests/memory-hotplug/on-off-test.sh
/linux-4.1.27/tools/
DMakefile57 $(call descend,testing/$@)
75 $(call descend,testing/$(@:_clean=),install)
107 $(call descend,testing/$(@:_clean=),clean)
/linux-4.1.27/tools/testing/selftests/rcutorture/bin/
Dkvm-recheck.sh27 PATH=`pwd`/tools/testing/selftests/rcutorture/bin:$PATH; export PATH
28 . tools/testing/selftests/rcutorture/bin/functions.sh
Dkvm-recheck-rcu.sh33 . tools/testing/selftests/rcutorture/bin/functions.sh
/linux-4.1.27/drivers/staging/lustre/lnet/
DKconfig16 tristate "Lustre networking self testing"
19 Choose Y here if you want to do lnet self testing. To compile this
/linux-4.1.27/tools/testing/ktest/examples/
DREADME10 crosstests.conf - this config shows an example of testing a git repo against
17 used to perform real testing.
/linux-4.1.27/drivers/scsi/aacraid/
DTODO2 o More testing
/linux-4.1.27/Documentation/RCU/
Dtorture.txt60 n_barrier_cbs If this is nonzero, RCU barrier testing will be conducted,
63 this testing. The value cannot be negative. If you
68 error will be reported and no testing will be carried out.
107 This capability is useful for automated testing.
142 RCU priority-inversion testing only if the selected
145 testing. Specifying "test_boost=2" performs RCU
146 priority-inversion testing even if the selected RCU
149 carry out RCU priority-inversion testing.
158 The number of seconds to do RCU priority-inversion testing
270 an RCU priority inversion condition. If you are testing RCU
Dlockdep.txt65 or coalescsing. This is useful when when testing the
70 or coalescsing. This is useful when when testing the
/linux-4.1.27/tools/testing/selftests/rcutorture/doc/
DTREE_RCU-kconfig.txt18 CONFIG_RCU_KTHREAD_PRIO -- set to 2 for _BOOST testing.
84 Always used in KVM testing.
DTINY_RCU.txt10 The theory here is that randconfig testing will hit the other six possible
Dinitrd.txt9 cd tools/testing/selftests/rcutorture
/linux-4.1.27/drivers/net/wireless/ath/
DKconfig46 bool "Atheros dynamic user regulatory testing"
51 undergoing certification testing.
/linux-4.1.27/lib/
DKconfig.kasan51 tristate "Module for testing kasan for bug detection"
55 out of bounds accesses, use after free. It is useful for testing
DKconfig.kgdb38 as well as regression testing the kgdb internals.
DKconfig.debug938 bool "Wait/wound mutex debugging: Slowpath testing"
944 This feature enables slowpath testing for w/w mutex users by
1274 This is useful when torture-testing RCU, but in almost no
1537 This module enables testing of the different dumping mechanisms by
1561 This option provides for testing basic kprobes functionality on
1722 user/kernel boundary testing is working. If it fails to load,
1748 interface for testing firmware loading. This can be used to
/linux-4.1.27/drivers/usb/usbip/
DREADME3 - testing
/linux-4.1.27/drivers/fmc/
DKconfig22 tristate "FMC fake device (software testing)"
29 tristate "FMC trivial mezzanine driver (software testing)"
/linux-4.1.27/crypto/asymmetric_keys/
DKconfig50 tristate "PKCS#7 testing key type"
60 This is intended for testing the PKCS#7 parser.
/linux-4.1.27/drivers/firmware/efi/
DKconfig16 <http://linux.dell.com/efibootmgr/testing/efibootmgr-0.5.0-test3.tar.gz>
48 See also Documentation/ABI/testing/sysfs-firmware-efi-runtime-map.
/linux-4.1.27/drivers/acpi/apei/
DKconfig54 mainly used for debugging and testing the other parts of
63 if you want to debugging and testing the ERST kernel support
/linux-4.1.27/Documentation/networking/
Deql.txt11 1.1.86. Some testing with 1.1.92 has been done with the v1.1 patch
29 my testing so far, the Livingston PortMaster 2e's load-balancing is a
225 I have not yet done any load-balancing testing for PPP devices, mainly
246 All testing I have done was with two 28.8 V.FC modems, one connecting
339 Although you may already done this performance testing, here
354 I have done some testing of this software, with two goals in
383 about 160 kbits/sec. The next round of testing will distribute
Dpktgen.txt312 ftp://robur.slu.se/pub/Linux/net-development/pktgen-testing/
313 ftp://robur.slu.se/pub/Linux/net-development/pktgen-testing/examples/
316 ftp://robur.slu.se/pub/Linux/net-development/pktgen-testing/pktgen_paper.pdf
319 Grant Grundler for testing on IA-64 and parisc, Harald Welte, Lennert Buytenhek
Dsctp.txt28 implementation and testing lksctp on IPv4.
Diphase.txt130 It is the same as the UBR testing, but with an extra command option:
136 It is the same as the UBR testing, but with an extra command option:
DREADME.ipw2200126 on the amount of validation and interoperability testing that has been
371 iwconfig eth1 mode ad-hoc essid testing channel 2
415 being made available for testing and cutting edge users. The stability
Dgeneric-hdlc.txt54 loopback - activate hardware loopback (for testing only)
Dltpc.txt127 work, and to Denis Hainsworth for doing the bleeding-edge testing.
Dnetdev-FAQ.txt202 Q: What level of testing is expected before I submit my change?
206 will have done run-time testing specific to your change, but at a
Dixgbe.txt55 have received some testing. Not all modules are applicable to all devices.
92 have received some testing. Not all modules are applicable to all devices.
Dde4x5.txt118 debt to <mjacob@feral.com> for the testing and feedback that helped get
D6pack.txt142 When testing the driver with 2.0.3x kernels and
Dudplite.txt99 For testing purposes, the following can serve as a `mini' header file:
DREADME.ipw2100103 on the amount of validation and interoperability testing that has been
/linux-4.1.27/Documentation/isdn/
DCREDITS44 For testing and help to get into kernel.
65 For heavy-duty-beta-testing with his BBS ;)
DREADME.x2548 For local testing it is also recommended to enable the isdnloop driver
51 For testing, it is recommended that all isdn drivers and the X.25 PLP
/linux-4.1.27/Documentation/ABI/
DREADME20 testing/
53 the "testing" stage, so that kernel developers can work
69 Interfaces in the testing state can move to the stable state when the
/linux-4.1.27/fs/logfs/
DKconfig15 not be used for other than testing purposes.
/linux-4.1.27/tools/testing/selftests/ftrace/
DREADME5 shell scripts for testing. Feel free to add new test cases.
38 * The test cases should run on dash (busybox shell) for testing on
/linux-4.1.27/Documentation/scsi/
Din2000.txt11 with. Done some heavy testing and it looks very good.
90 testing and optimizing: I think there's a real improvement
137 spent a lot of time testing this. You might try 'ENABLE_CLUSTERING'
197 Willmore for extensive 'bonnie' testing. And to Joe Mack for
198 continual testing and feedback.
DFlashPoint.txt141 subsequent releases. As a result of this cooperative testing process,
143 test system provided an ideal environment for testing error recovery
149 embedded system. I am presently working on some performance testing and
Dadvansys.txt202 Erik Ratcliffe <erik@caldera.com> has done testing of the
213 suggestions to improve the driver and done a lot of testing.
243 Ken Witherow for extensive testing during the development of version 3.4.
Ddpti.txt36 * V2.1 Internal testing
Dosd.txt23 This is a SCSI ULD that registers for OSD type devices and provides a testing
DChangeLog.sym53c8xx341 to testing for a PHASE. SYMBIOS say this feature is working fine.
470 - I received this afternoon a 896 from SYMBIOS and started testing
586 - Do some testing with io_mapped and fix what needed to be so.
DChangeLog.ncr53c8xx367 - Some simplification for 64 bit arch done ccb address testing.
425 having won arbitration, do some stuff prior to testing any SCSI
Dtmscsim.txt49 fixes to people for testing, I create intermediate versions with a digit
425 Tonneau) for intensively testing the driver (and even risking data loss
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-bus-iio-trigger-sysfs9 automated testing or in situations, where other trigger methods
Dsysfs-bus-usb-lvstest1 Link Layer Validation Device is a standard device for testing of Super
Dsysfs-class-uwb_rc-wusbhc33 This is only of limited use for testing and
Dsysfs-block-bcache76 for benchmarking/testing.
Dsysfs-class-net180 "unknown", "notpresent", "down", "lowerlayerdown", "testing",
/linux-4.1.27/drivers/staging/ozwpan/
DTODO10 - testing with as many devices as possible.
/linux-4.1.27/Documentation/spi/
D00-INDEX22 - SPI testing utility.
Dep93xx_spi104 the driver. Simplemachines.it donated me a Sim.One board which I used testing
Dpxa2xx131 testing.
/linux-4.1.27/drivers/staging/iio/
DTODO5 2) Additional testing
59 2) Lots of testing
DKconfig27 a driver. May also be useful for testing userspace code
/linux-4.1.27/drivers/media/platform/vivid/
DKconfig17 It is highly configurable and is ideal for testing applications.
/linux-4.1.27/Documentation/cpuidle/
Dcore.txt21 is meant for developer testing only. In normal usage, kernel picks the
Dsysfs.txt14 With cpuidle_sysfs_switch boot option (meant for developer testing)
/linux-4.1.27/Documentation/leds/
Dleds-class-flash.txt16 (see Documentation/ABI/testing/sysfs-class-led-flash)
/linux-4.1.27/Documentation/cgroups/
D00-INDEX20 - Memory Resource Controller; design, accounting, interface, testing.
/linux-4.1.27/Documentation/networking/mac80211_hwsim/
DREADME17 to mac80211 are needed to use this testing tool.
38 complete testing of encryption.
/linux-4.1.27/drivers/net/wireless/ath/ath9k/
DKconfig107 bool "Atheros ath9k TX99 testing support"
112 certification testing and evaluation in a controlled environment.
116 TX99 support enables Specific Absorption Rate (SAR) testing.
/linux-4.1.27/arch/arm/mach-u300/
DKconfig40 to test reference designs. If you're not testing SPI,
/linux-4.1.27/Documentation/security/
DSELinux.txt7 testing, you can do using 'mdp' provided under
/linux-4.1.27/drivers/staging/android/ion/
DKconfig26 be used for testing the ION infrastructure if
/linux-4.1.27/Documentation/usb/
Dgadget_multi.txt73 Please note, that while testing we encountered some issues[6] when
100 **** INF testing
116 Any testing and drivers *are* *welcome*!
Dmtouchusb.txt72 testing!
Drio.txt59 for .fon files and also does testing. The program will mostly sure be
Derror-codes.txt74 these values on one CPU, and device drivers testing them on another CPU.
Dgadget-testing.txt1 This file summarizes information on basic testing of USB functions
745 The most basic testing:
771 More advanced testing can be done with the prn_example
Dusb-serial.txt276 to implement and final testing and debugging to do. The parallel port
344 The driver is generally working, though it still needs some more testing.
Dehci.txt133 However, do make a point of testing device drivers through USB 2.0 hubs.
/linux-4.1.27/arch/arm/boot/dts/
Ds5pv210-smdkc110.dts13 * support. Due to lack of hardware, _no_ testing has been performed.
Ds5pv210-torbreck.dts13 * support. Due to lack of hardware, _no_ testing has been performed.
Ds5pv210-smdkv210.dts13 * support. Due to lack of hardware, _no_ testing has been performed.
/linux-4.1.27/Documentation/power/
Dinterface.txt24 system (for testing).
26 Additionally, /sys/power/disk can be used to turn on one of the two testing
D00-INDEX11 drivers-testing.txt
Ddrivers-testing.txt17 testing the new driver. Please see Documentation/power/basic-pm-debugging.txt
Dbasic-pm-debugging.txt41 To find out why hibernation fails on your system, you can use a special testing
195 Among other things, the testing with the help of /sys/power/pm_test may allow
/linux-4.1.27/Documentation/vm/
Dhwpoison.txt102 Poison a page in the process for testing
129 This should be only used for testing with artificial injection.
152 This allows stress testing of many kinds of pages. The page_flags
Dhugetlbpage.txt326 1) map_hugetlb: see tools/testing/selftests/vm/map_hugetlb.c
328 2) hugepage-shm: see tools/testing/selftests/vm/hugepage-shm.c
330 3) hugepage-mmap: see tools/testing/selftests/vm/hugepage-mmap.c
Dnuma63 physical memory. NUMA emluation is useful for testing NUMA kernel and
Dunevictable-lru.txt200 page_evictable() also checks for mlocked pages by testing an additional page
444 can skip these pages by testing the page mapping under page lock.
572 mapped in a given VMA - either for unmapping or testing whether the
/linux-4.1.27/Documentation/sound/alsa/
DREADME.maya4416 This is the first testing version of the Maya44 driver released to the alsa-devel mailing list (Feb…
37 *In particular, we would appreciate testing of these functions by anyone who has access to an M/IO/…
148 H/W 4 ... H/W 9: unknown function, left in to enable testing.
DHD-Audio-Models.txt138 test for testing/debugging purpose, almost all controls
147 test for testing/debugging purpose, almost all controls
/linux-4.1.27/net/decnet/
DTODO15 o Lots of testing with real applications
/linux-4.1.27/Documentation/filesystems/cifs/
DTODO91 Misc testing to do
99 3) Additional performance testing and optimization using iozone and similar -
DAUTHORS39 Gunter Kukkukk (testing and suggestions for support of old servers)
/linux-4.1.27/Documentation/cdrom/
Dpacket-writing.txt112 Documentation/ABI/testing/sysfs-class-pktcdvd
124 Documentation/ABI/testing/debugfs-pktcdvd
/linux-4.1.27/drivers/usb/misc/
DKconfig145 the PCCARD. A rather pointless thing to do, but useful for testing.
193 tristate "USB testing driver"
195 This driver is for testing host controller software. It is used
196 with specialized device firmware for regression and stress testing,
/linux-4.1.27/Documentation/i2c/busses/
Di2c-sis63053 - testing SiS730 support
Di2c-ali153526 observed through testing. These changes are reflected in this driver and
Di2c-taos-evm46 practice, as these modules are meant for evaluation and testing only.
Di2c-sis96x66 - testing for SiS645DX
Di2c-i801146 drivers/pci/quirks.c. Then please give it very good testing, to make sure
/linux-4.1.27/Documentation/fmc/
Dfmc-fakedev.txt24 [ 99.979624] Product name: fake-design-for-testing
Dfmc-write-eeprom.txt68 [ 72.989434] fake-fmc: Product name: fake-design-for-testing
/linux-4.1.27/Documentation/xtensa/
Datomctl.txt30 Developers might find using RCW in Bypass mode convenient when testing
/linux-4.1.27/drivers/scsi/osd/
DKconfig27 to user-mode for testing and controlling OSD devices. It is also
/linux-4.1.27/Documentation/zh_CN/
DSubmittingDrivers108 Documentation/power/drivers-testing.txt。有关驱动程序电
/linux-4.1.27/drivers/net/wireless/
DKconfig247 tristate "Simulated radio testing tool for mac80211"
250 This driver is a developer testing tool that can be used to test
252 needed for normal wireless LAN usage and is only for testing. See
/linux-4.1.27/Documentation/device-mapper/
Ddm-flakey.txt6 failing devices for testing purposes.
Dzero.txt16 device is deactivated. This can be very useful for testing device and
/linux-4.1.27/Documentation/hwmon/
Dpc8742713 Michael Kress for testing several iterations of this driver.
Dds162161 A second thing is that, during extensive testing, Tout showed a tolerance
73 reset. Be aware: When testing, it showed that the status of Tout can change
Dabituguru341 Default: 1 (the driver is still in the testing phase)
Dabituguru65 Default: 2 (the driver is still in the testing phase)
Dzl6100101 appears to be sufficient and has not caused any problems in testing. The problem
Dsubmitting-patches26 architecture. If run-time testing was not achieved, it should be written
Dabituguru-datasheet42 After wider testing of the Linux kernel driver some variants of the uGuru have
153 After wider testing of the Linux kernel driver some variants of the uGuru have
Dpc8736012 Thanks to Sandeep Mehta, Tonko de Rooy and Daniel Ceregatti for testing.
Dlm85107 steps, but in initial testing of the ADM1027 it was 1.00 degC steps. Analog
/linux-4.1.27/drivers/net/wireless/ath/ath5k/
DKconfig70 bool "Enables testing channels on ath5k"
/linux-4.1.27/Documentation/timers/
Dhrtimers.txt10 features into the existing timer framework, and after testing various
148 hrtimers - testing and verification
176 code got a healthy amount of testing and use in practice.
DNO_HZ.txt28 discussing testing, and a fifth and final section listing known issues.
241 git://git.kernel.org/pub/scm/linux/kernel/git/frederic/dynticks-testing.git
/linux-4.1.27/Documentation/filesystems/
Dautofs4-mount-control.txt75 / shark:/autofs/export5/testing/test \
76 /s1 shark:/autofs/export/testing/test/s1 \
77 /s2 shark:/autofs/export5/testing/test/s2 \
84 / shark:/autofs/export5/testing/test \
85 /s1 shark:/autofs/export/testing/test/s1 \
86 /s2 shark:/autofs/export5/testing/test/s2 \
Dlogfs.txt194 collisions necessary to overflow a bucket, but testing showed that in
/linux-4.1.27/drivers/virtio/
DKconfig36 break. Otherwise, leave it set. Unless you're testing what
/linux-4.1.27/drivers/media/platform/soc_camera/
DKconfig18 This is a generic SoC camera platform driver, useful for testing
/linux-4.1.27/drivers/mmc/card/
DKconfig70 testing a host driver. Most people should say N here.
/linux-4.1.27/drivers/media/rc/img-ir/
DKconfig18 testing, debug, and to make more protocols available.
/linux-4.1.27/arch/x86/
DKconfig.debug175 code to do real stress testing of the IOMMU code. This option
177 testing.
317 This option enables automated sanity testing of the IMR code.
/linux-4.1.27/drivers/media/pci/zoran/
Dzoran.h363 int testing; member
Dzoran_card.c947 zr->testing = 0; in zoran_open_init_params()
957 zr->testing = 1; in test_interrupts()
965 zr->testing = 0; in test_interrupts()
/linux-4.1.27/tools/perf/tests/attr/
DREADME3 This testing support is embedded into perf directly and is governed
/linux-4.1.27/net/bluetooth/
DKconfig68 bool "Bluetooth self testing support"
/linux-4.1.27/Documentation/misc-devices/
Dc2port.txt42 boundary-scan testing on low pin-count Silicon Labs devices. Currently
/linux-4.1.27/Documentation/driver-model/
Ddevres.txt34 attention or testing as core code, and bugs on driver detach or
133 shared with exit path, both can get more testing.
/linux-4.1.27/arch/arm64/
DKconfig.debug53 This option is intended for bootloader and/or kernel testing
/linux-4.1.27/Documentation/ptp/
Dptp.txt36 cases, only one PTP clock is needed. However, for testing and
/linux-4.1.27/Documentation/x86/x86_64/
Dmachinecheck61 3: never panic or SIGBUS, log all errors (for testing only)
Dboot-options.txt47 3: never panic or SIGBUS, log all errors (for testing only)
/linux-4.1.27/Documentation/arm/Samsung-S3C24XX/
DSuspend.txt59 The following is an example of code used for testing wakeup from
/linux-4.1.27/Documentation/s390/
DDASD25 We performed our testing on 3380 and 3390 type disks of different
D3270.txt130 Here are the testing steps in detail:
268 Happy testing! I welcome any and all comments about this document, the
/linux-4.1.27/sound/oss/
DCHANGELOG214 - Huge amount of testing (more testing is still required).
215 - mmap() support (works with some cards). Requires much more testing.
/linux-4.1.27/Documentation/input/
Djoystick.txt56 For testing and other purposes (for example serial devices), a set of
77 For testing with inpututils it's also convenient to create these:
116 For testing the joystick driver functionality, there is the jstest
544 testing whether the driver works, if in doubt, use the jstest utility in
Dntrig.txt116 The N-Trig windows tools provide calibration and testing routines. Also an
/linux-4.1.27/tools/power/cpupower/bench/
DREADME-BENCH13 - Possibly Real time priority testing? -> what happens if there are
/linux-4.1.27/fs/nfsd/
DKconfig115 testing error recovery on the NFS client.
/linux-4.1.27/Documentation/firmware_class/
DREADME87 for testing and completeness, they are not called in normal use.
/linux-4.1.27/arch/mn10300/
DKconfig.debug30 for kernel debugging, non-intrusive instrumentation and testing.
/linux-4.1.27/kernel/power/
DKconfig155 bool "Extra PM attributes in sysfs for low-level debugging/testing"
160 developer interested in debugging/testing Power Management, say "no".
/linux-4.1.27/drivers/md/
DKconfig165 features and more testing.
174 read or write errors. It is useful for testing.
412 them to different devices. Useful for testing.
/linux-4.1.27/Documentation/video4linux/
Dsi476x.txt19 useful for EoL testing/RF performance estimation, parameters that have
Dvivid.txt7 testing capture and output overlays.
31 - All Field settings are supported for testing interlaced capturing
104 bit 16: Framebuffer for testing overlays
581 testing colorspace conversions: the colors used in that test pattern
1003 data_offset to be non-zero, so this is a useful feature for testing applications.
1016 used for testing this API. Whether this API should be used for new drivers is
1110 - Some support for testing compressed video
1115 - Add ARGB888 overlay support: better testing of the alpha channel
Dsi470x.txt49 Testing is usually done with most application under Debian/testing:
Duvcvideo.txt55 For applications that need to access XU controls directly, e.g. for testing
/linux-4.1.27/Documentation/dvb/
Dcards.txt20 - dvb_dummy_fe: for testing...
Dfaq.txt15 are mainly intended for testing and to demonstrate how the
/linux-4.1.27/drivers/net/wireless/iwlwifi/
DKconfig138 Enable use of experimental ucode for testing and debugging.
/linux-4.1.27/drivers/firmware/
DKconfig37 See also Documentation/ABI/testing/sysfs-firmware-memmap.
/linux-4.1.27/drivers/isdn/i4l/
DKconfig97 testing of linklevel features or configuration without getting
/linux-4.1.27/arch/alpha/lib/
Dstxcpy.S148 cmpbge zero, t2, t8 # e0 : testing eos
Dev6-stxcpy.S171 cmpbge zero, t2, t8 # E : testing eos (stall)
/linux-4.1.27/net/
DKconfig296 menu "Network testing"
304 stress testing and performance analysis. If you don't understand
/linux-4.1.27/fs/jffs2/
DKconfig21 testing and debugging, it's advisable to set it to one. This will
/linux-4.1.27/Documentation/power/regulator/
Doverview.txt171 See Documentation/ABI/testing/sysfs-class-regulator
/linux-4.1.27/Documentation/locking/
Dlocktorture.txt68 This capability is useful for automated testing.
/linux-4.1.27/Documentation/scheduler/
Dsched-deadline.txt120 * to come back here and continue reading (once the urge for testing is
358 The first testing application is called rt-app and can be used to
386 The second testing application is a modification of schedtool, called
/linux-4.1.27/Documentation/cris/
DREADME100 POSIX conformance testing by UNIFIX
/linux-4.1.27/Documentation/aoe/
Daoe.txt129 is supported for testing purposes and makes the aoe driver keep
/linux-4.1.27/arch/m68k/q40/
DREADME70 for first testing. The Q40 does not support DMA and may have trouble with
/linux-4.1.27/Documentation/blockdev/
Dzram.txt104 read Documentation/ABI/testing/sysfs-block-zram.
/linux-4.1.27/fs/befs/
DChangeLog207 testing purposes. (fs/Config.in)
217 I've done some serious testing on it now (on my box anyhow), and it
/linux-4.1.27/Documentation/acpi/apei/
Deinj.txt5 for debugging and testing APEI and RAS features in general.
/linux-4.1.27/sound/drivers/
DKconfig72 You don't need this unless you're testing the hardware support
/linux-4.1.27/drivers/staging/speakup/
DKconfig189 tristate "Dummy synthesizer driver (for testing)"
/linux-4.1.27/arch/m68k/fpsp040/
Dskeleton.S48 | The following counters are used for standalone testing
/linux-4.1.27/drivers/usb/host/
DKconfig655 the PCCARD. A rather pointless thing to do, but useful for testing.
784 or embedded hosts that need to undergo USB-IF compliance testing with
785 the aid of special testing hardware. In the future, this may expand
/linux-4.1.27/init/
DKconfig560 This option stands for testing when an arch implements the
590 systems, but if you are stress-testing the RCU implementation
594 Select a specific number if testing RCU itself.
618 Select a specific number if testing RCU itself.
631 testing RCU itself, and might one day be useful on systems with
763 boot time, for example, to allow testing of different no-CBs
778 is to ensure that randconfig testing covers mixed systems.
/linux-4.1.27/drivers/mtd/devices/
DKconfig152 testing stuff.
/linux-4.1.27/Documentation/serial/
Dmoxa-smartio70 - msterm A simple terminal program which is useful in testing serial
453 especially for MOXA ports. It is quite useful for testing simple
/linux-4.1.27/drivers/platform/x86/
DKconfig546 <file:Documentation/ABI/testing/sysfs-platform-asus-wmi>
559 <file:Documentation/ABI/testing/sysfs-platform-asus-wmi>
812 <file:Documentation/ABI/testing/sysfs-platform-samsung-laptop>
/linux-4.1.27/arch/xtensa/configs/
Dcommon_defconfig278 # Network testing
/linux-4.1.27/drivers/input/serio/
DKconfig151 more testing.
/linux-4.1.27/arch/microblaze/boot/dts/
Dsystem.dts36 model = "testing";
/linux-4.1.27/arch/powerpc/boot/dts/
Dvirtex440-ml507.dts28 model = "testing";
/linux-4.1.27/Documentation/filesystems/nfs/
Dnfs-rdma.txt27 In our testing, we have obtained excellent performance results (full 10Gbit
/linux-4.1.27/kernel/trace/
DKconfig510 This option will also enable testing every syscall event.
535 This is a dumb module for testing mmiotrace. It is very dangerous
/linux-4.1.27/Documentation/arm64/
Dacpi_object_usage.txt84 This table is very useful for testing platform response to error
88 and executed with the ACPICA tools only during testing.
/linux-4.1.27/Documentation/virtual/kvm/
Dmsr.txt261 in the window between guest testing it to detect

12