/linux-4.4.14/Documentation/ |
D | kselftest.txt | 3 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 61 location which is tools/testing/selftests/kselftest or an user specified 65 $ cd tools/testing/selftests 69 $ cd tools/testing/selftests
|
D | xz.txt | 30 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
|
D | SubmittingDrivers | 99 anything. For the driver testing instructions see 100 Documentation/power/drivers-testing.txt and for a relatively
|
D | applying-patches.txt | 223 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
|
D | Intel-IOMMU.txt | 109 - For compatibility testing, could use unity map domain for all devices, just
|
D | hw_random.txt | 90 did the "brains" and all the testing.
|
D | SubmitChecklist | 40 combinations. This is very hard to get right with testing -- brainpower
|
D | bcache.txt | 193 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
|
D | svga.txt | 255 - Hardware testing order slightly changed, tests based on ROM 271 - Direct testing of SVGA adapters turned off by default, `scan'
|
D | stable_kernel_rules.txt | 64 a public git tree (for instance, because it deserves more regression testing
|
D | gcov.txt | 18 gcov profiling kernel support enables the use of GCC's coverage testing
|
D | adding-syscalls.txt | 178 selftest in tools/testing/selftests/. 450 program in a new directory under tools/testing/selftests/. 461 For more extensive and thorough testing of new functionality, you should also
|
D | HOWTO | 249 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
|
D | kmemleak.txt | 113 you can find new unreferenced objects; this should help with testing
|
/linux-4.4.14/Documentation/fault-injection/ |
D | fault-injection.txt | 257 tools/testing/fault-injection/failcmd.sh. Please run a command 258 "./tools/testing/fault-injection/failcmd.sh --help" for more information and 263 Run a command "make -C tools/testing/selftests/ run_tests" with injecting slab 266 # ./tools/testing/fault-injection/failcmd.sh \ 267 -- make -C tools/testing/selftests/ run_tests 272 # ./tools/testing/fault-injection/failcmd.sh --times=100 \ 273 -- make -C tools/testing/selftests/ run_tests 279 ./tools/testing/fault-injection/failcmd.sh --times=100 \ 280 -- make -C tools/testing/selftests/ run_tests
|
D | notifier-error-inject.txt | 92 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.4.14/tools/ |
D | Makefile | 73 $(call descend,testing/$@) 99 $(call descend,testing/$(@:_clean=),install) 134 $(call descend,testing/$(@:_clean=),clean)
|
/linux-4.4.14/tools/testing/selftests/rcutorture/bin/ |
D | kvm-recheck.sh | 27 PATH=`pwd`/tools/testing/selftests/rcutorture/bin:$PATH; export PATH 28 . tools/testing/selftests/rcutorture/bin/functions.sh
|
D | kvm-recheck-rcu.sh | 33 . tools/testing/selftests/rcutorture/bin/functions.sh
|
/linux-4.4.14/drivers/staging/lustre/lnet/ |
D | Kconfig | 16 tristate "Lustre networking self testing" 19 Choose Y here if you want to do lnet self testing. To compile this
|
/linux-4.4.14/tools/testing/ktest/examples/ |
D | README | 10 crosstests.conf - this config shows an example of testing a git repo against 17 used to perform real testing.
|
/linux-4.4.14/drivers/scsi/aacraid/ |
D | TODO | 2 o More testing
|
/linux-4.4.14/Documentation/RCU/ |
D | torture.txt | 60 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 257 an RCU priority inversion condition. If you are testing RCU
|
D | lockdep.txt | 60 or coalescsing. This is useful when when testing the
|
/linux-4.4.14/lib/ |
D | Kconfig.kasan | 46 tristate "Module for testing kasan for bug detection" 50 out of bounds accesses, use after free. It is useful for testing
|
D | Kconfig.kgdb | 38 as well as regression testing the kgdb internals.
|
D | Kconfig.debug | 947 bool "Wait/wound mutex debugging: Slowpath testing" 953 This feature enables slowpath testing for w/w mutex users by 1285 of CPUs. This is useful when torture-testing RCU, but in 1310 This is useful when torture-testing RCU, but in almost no 1335 torture-testing RCU, but in almost no other circumstance. 1601 This module enables testing of the different dumping mechanisms by 1625 This option provides for testing basic kprobes functionality on 1789 user/kernel boundary testing is working. If it fails to load, 1815 interface for testing firmware loading. This can be used to
|
/linux-4.4.14/tools/testing/selftests/rcutorture/doc/ |
D | TREE_RCU-kconfig.txt | 18 CONFIG_RCU_KTHREAD_PRIO -- set to 2 for _BOOST testing. 73 Always used in KVM testing.
|
D | TINY_RCU.txt | 10 The theory here is that randconfig testing will hit the other six possible
|
D | initrd.txt | 9 cd tools/testing/selftests/rcutorture
|
/linux-4.4.14/drivers/net/wireless/ath/ |
D | Kconfig | 46 bool "Atheros dynamic user regulatory testing" 51 undergoing certification testing.
|
/linux-4.4.14/drivers/usb/usbip/ |
D | README | 3 - testing
|
/linux-4.4.14/drivers/fmc/ |
D | Kconfig | 22 tristate "FMC fake device (software testing)" 29 tristate "FMC trivial mezzanine driver (software testing)"
|
/linux-4.4.14/drivers/acpi/apei/ |
D | Kconfig | 54 mainly used for debugging and testing the other parts of 63 if you want to debugging and testing the ERST kernel support
|
/linux-4.4.14/crypto/asymmetric_keys/ |
D | Kconfig | 50 tristate "PKCS#7 testing key type" 60 This is intended for testing the PKCS#7 parser.
|
/linux-4.4.14/Documentation/networking/ |
D | eql.txt | 11 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
|
D | pktgen.txt | 380 ftp://robur.slu.se/pub/Linux/net-development/pktgen-testing/ 381 ftp://robur.slu.se/pub/Linux/net-development/pktgen-testing/examples/ 384 ftp://robur.slu.se/pub/Linux/net-development/pktgen-testing/pktgen_paper.pdf 387 Grant Grundler for testing on IA-64 and parisc, Harald Welte, Lennert Buytenhek
|
D | sctp.txt | 28 implementation and testing lksctp on IPv4.
|
D | iphase.txt | 130 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:
|
D | README.ipw2200 | 126 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
|
D | generic-hdlc.txt | 54 loopback - activate hardware loopback (for testing only)
|
D | ltpc.txt | 127 work, and to Denis Hainsworth for doing the bleeding-edge testing.
|
D | netdev-FAQ.txt | 202 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
|
D | ixgbe.txt | 55 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.
|
D | de4x5.txt | 118 debt to <mjacob@feral.com> for the testing and feedback that helped get
|
D | 6pack.txt | 142 When testing the driver with 2.0.3x kernels and
|
D | udplite.txt | 99 For testing purposes, the following can serve as a `mini' header file:
|
/linux-4.4.14/Documentation/isdn/ |
D | CREDITS | 44 For testing and help to get into kernel. 65 For heavy-duty-beta-testing with his BBS ;)
|
D | README.x25 | 48 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.4.14/Documentation/ABI/ |
D | README | 20 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.4.14/drivers/gpu/drm/amd/amdgpu/ |
D | Kconfig | 9 is for experimentation and testing.
|
/linux-4.4.14/fs/logfs/ |
D | Kconfig | 15 not be used for other than testing purposes.
|
/linux-4.4.14/tools/testing/selftests/ftrace/ |
D | README | 5 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.4.14/Documentation/scsi/ |
D | in2000.txt | 11 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.
|
D | FlashPoint.txt | 141 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
|
D | advansys.txt | 202 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.
|
D | dpti.txt | 36 * V2.1 Internal testing
|
D | osd.txt | 23 This is a SCSI ULD that registers for OSD type devices and provides a testing
|
D | ChangeLog.sym53c8xx | 341 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.
|
/linux-4.4.14/Documentation/spi/ |
D | 00-INDEX | 22 - SPI testing utility.
|
D | ep93xx_spi | 104 the driver. Simplemachines.it donated me a Sim.One board which I used testing
|
D | pxa2xx | 125 testing.
|
/linux-4.4.14/drivers/staging/iio/ |
D | TODO | 5 2) Additional testing 59 2) Lots of testing
|
D | Kconfig | 28 a driver. May also be useful for testing userspace code
|
/linux-4.4.14/drivers/firmware/efi/ |
D | Kconfig | 16 <http://linux.dell.com/efibootmgr/testing/efibootmgr-0.5.0-test3.tar.gz> 53 See also Documentation/ABI/testing/sysfs-firmware-efi-runtime-map.
|
/linux-4.4.14/Documentation/cpuidle/ |
D | core.txt | 21 is meant for developer testing only. In normal usage, kernel picks the
|
D | sysfs.txt | 14 With cpuidle_sysfs_switch boot option (meant for developer testing)
|
/linux-4.4.14/Documentation/networking/mac80211_hwsim/ |
D | README | 17 to mac80211 are needed to use this testing tool. 38 complete testing of encryption.
|
/linux-4.4.14/drivers/hwtracing/stm/ |
D | Kconfig | 16 and discards your data. Use for stm class testing.
|
/linux-4.4.14/Documentation/cgroups/ |
D | 00-INDEX | 20 - Memory Resource Controller; design, accounting, interface, testing.
|
/linux-4.4.14/drivers/net/wireless/ath/ath9k/ |
D | Kconfig | 107 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.4.14/arch/arm/mach-u300/ |
D | Kconfig | 40 to test reference designs. If you're not testing SPI,
|
/linux-4.4.14/drivers/media/platform/vivid/ |
D | Kconfig | 17 It is highly configurable and is ideal for testing applications.
|
/linux-4.4.14/tools/testing/selftests/zram/ |
D | README | 29 Commands required for testing:
|
/linux-4.4.14/drivers/staging/rdma/hfi1/ |
D | Kconfig | 13 sdma completions for unit testing
|
/linux-4.4.14/drivers/staging/android/ion/ |
D | Kconfig | 26 be used for testing the ION infrastructure if
|
/linux-4.4.14/Documentation/security/ |
D | SELinux.txt | 7 testing, you can do using 'mdp' provided under
|
/linux-4.4.14/Documentation/usb/ |
D | gadget_multi.txt | 73 Please note, that while testing we encountered some issues[6] when 100 **** INF testing 116 Any testing and drivers *are* *welcome*!
|
D | mtouchusb.txt | 72 testing!
|
D | rio.txt | 59 for .fon files and also does testing. The program will mostly sure be
|
D | error-codes.txt | 74 these values on one CPU, and device drivers testing them on another CPU.
|
D | gadget-testing.txt | 1 This file summarizes information on basic testing of USB functions 743 The most basic testing: 769 More advanced testing can be done with the prn_example
|
D | usb-serial.txt | 276 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.
|
/linux-4.4.14/arch/arm/boot/dts/ |
D | s5pv210-smdkc110.dts | 13 * support. Due to lack of hardware, _no_ testing has been performed.
|
D | s5pv210-torbreck.dts | 13 * support. Due to lack of hardware, _no_ testing has been performed.
|
D | s5pv210-smdkv210.dts | 13 * support. Due to lack of hardware, _no_ testing has been performed.
|
/linux-4.4.14/Documentation/power/ |
D | interface.txt | 24 system (for testing). 26 Additionally, /sys/power/disk can be used to turn on one of the two testing
|
D | 00-INDEX | 11 drivers-testing.txt
|
D | drivers-testing.txt | 17 testing the new driver. Please see Documentation/power/basic-pm-debugging.txt
|
D | basic-pm-debugging.txt | 41 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.4.14/Documentation/trace/ |
D | intel_th.txt | 30 Documentation/ABI/testing/sysfs-bus-intel_th-output-devices, the most 36 description is at Documentation/ABI/testing/sysfs-bus-intel_th-devices-gth.
|
/linux-4.4.14/Documentation/sound/alsa/ |
D | README.maya44 | 16 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.
|
D | HD-Audio-Models.txt | 148 test for testing/debugging purpose, almost all controls 157 test for testing/debugging purpose, almost all controls
|
/linux-4.4.14/Documentation/vm/ |
D | hwpoison.txt | 102 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
|
D | hugetlbpage.txt | 326 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 336 Kernel development regression testing
|
D | numa | 63 physical memory. NUMA emluation is useful for testing NUMA kernel and
|
/linux-4.4.14/net/decnet/ |
D | TODO | 15 o Lots of testing with real applications
|
/linux-4.4.14/Documentation/cdrom/ |
D | packet-writing.txt | 112 Documentation/ABI/testing/sysfs-class-pktcdvd 124 Documentation/ABI/testing/debugfs-pktcdvd
|
/linux-4.4.14/Documentation/filesystems/cifs/ |
D | TODO | 91 Misc testing to do 99 3) Additional performance testing and optimization using iozone and similar -
|
D | AUTHORS | 39 Gunter Kukkukk (testing and suggestions for support of old servers)
|
/linux-4.4.14/drivers/usb/misc/ |
D | Kconfig | 145 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.4.14/Documentation/i2c/busses/ |
D | i2c-sis630 | 53 - testing SiS730 support
|
D | i2c-taos-evm | 46 practice, as these modules are meant for evaluation and testing only.
|
D | i2c-ali1535 | 26 observed through testing. These changes are reflected in this driver and
|
D | i2c-sis96x | 66 - testing for SiS645DX
|
D | i2c-i801 | 149 drivers/pci/quirks.c. Then please give it very good testing, to make sure
|
/linux-4.4.14/Documentation/xtensa/ |
D | atomctl.txt | 30 Developers might find using RCW in Bypass mode convenient when testing
|
/linux-4.4.14/Documentation/fmc/ |
D | fmc-fakedev.txt | 24 [ 99.979624] Product name: fake-design-for-testing
|
D | fmc-write-eeprom.txt | 68 [ 72.989434] fake-fmc: Product name: fake-design-for-testing
|
/linux-4.4.14/drivers/scsi/osd/ |
D | Kconfig | 27 to user-mode for testing and controlling OSD devices. It is also
|
/linux-4.4.14/Documentation/zh_CN/ |
D | SubmittingDrivers | 108 Documentation/power/drivers-testing.txt。有关驱动程序电
|
/linux-4.4.14/drivers/net/wireless/ |
D | Kconfig | 247 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.4.14/Documentation/device-mapper/ |
D | dm-flakey.txt | 6 failing devices for testing purposes.
|
D | zero.txt | 16 device is deactivated. This can be very useful for testing device and
|
/linux-4.4.14/Documentation/ABI/testing/ |
D | sysfs-bus-usb-lvstest | 1 Link Layer Validation Device is a standard device for testing of Super
|
D | sysfs-bus-iio-trigger-sysfs | 9 automated testing or in situations, where other trigger methods
|
D | sysfs-class-uwb_rc-wusbhc | 33 This is only of limited use for testing and
|
D | sysfs-block-bcache | 76 for benchmarking/testing.
|
D | sysfs-class-net | 199 "unknown", "notpresent", "down", "lowerlayerdown", "testing",
|
/linux-4.4.14/drivers/net/wireless/ath/ath5k/ |
D | Kconfig | 69 bool "Enables testing channels on ath5k"
|
/linux-4.4.14/Documentation/hwmon/ |
D | pc87427 | 13 Michael Kress for testing several iterations of this driver.
|
D | ds1621 | 61 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
|
D | abituguru3 | 41 Default: 1 (the driver is still in the testing phase)
|
D | abituguru | 65 Default: 2 (the driver is still in the testing phase)
|
D | zl6100 | 101 appears to be sufficient and has not caused any problems in testing. The problem
|
D | submitting-patches | 26 architecture. If run-time testing was not achieved, it should be written
|
D | abituguru-datasheet | 42 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
|
D | pc87360 | 12 Thanks to Sandeep Mehta, Tonko de Rooy and Daniel Ceregatti for testing.
|
/linux-4.4.14/Documentation/timers/ |
D | hrtimers.txt | 10 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.
|
D | NO_HZ.txt | 28 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.4.14/Documentation/filesystems/ |
D | autofs4-mount-control.txt | 75 / 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 \
|
D | logfs.txt | 194 collisions necessary to overflow a bucket, but testing showed that in
|
/linux-4.4.14/drivers/virtio/ |
D | Kconfig | 36 break. Otherwise, leave it set. Unless you're testing what
|
/linux-4.4.14/drivers/media/platform/soc_camera/ |
D | Kconfig | 18 This is a generic SoC camera platform driver, useful for testing
|
/linux-4.4.14/drivers/media/rc/img-ir/ |
D | Kconfig | 18 testing, debug, and to make more protocols available.
|
/linux-4.4.14/drivers/mmc/card/ |
D | Kconfig | 70 testing a host driver. Most people should say N here.
|
/linux-4.4.14/drivers/media/pci/zoran/ |
D | zoran.h | 366 int testing; member
|
D | zoran_card.c | 947 zr->testing = 0; in zoran_open_init_params() 957 zr->testing = 1; in test_interrupts() 965 zr->testing = 0; in test_interrupts()
|
/linux-4.4.14/drivers/mailbox/ |
D | Kconfig | 85 Test client to help with testing new Controller driver
|
/linux-4.4.14/Documentation/misc-devices/ |
D | c2port.txt | 42 boundary-scan testing on low pin-count Silicon Labs devices. Currently
|
/linux-4.4.14/tools/perf/tests/attr/ |
D | README | 3 This testing support is embedded into perf directly and is governed
|
/linux-4.4.14/net/bluetooth/ |
D | Kconfig | 73 bool "Bluetooth self testing support"
|
/linux-4.4.14/Documentation/driver-model/ |
D | devres.txt | 34 attention or testing as core code, and bugs on driver detach or 133 shared with exit path, both can get more testing.
|
/linux-4.4.14/Documentation/leds/ |
D | leds-class-flash.txt | 16 (see Documentation/ABI/testing/sysfs-class-led-flash)
|
/linux-4.4.14/arch/x86/ |
D | Kconfig.debug | 208 code to do real stress testing of the IOMMU code. This option 210 testing. 362 This option enables automated sanity testing of the IMR code.
|
/linux-4.4.14/arch/arm64/ |
D | Kconfig.debug | 49 This option is intended for bootloader and/or kernel testing
|
/linux-4.4.14/Documentation/ptp/ |
D | ptp.txt | 36 cases, only one PTP clock is needed. However, for testing and
|
/linux-4.4.14/Documentation/x86/x86_64/ |
D | machinecheck | 61 3: never panic or SIGBUS, log all errors (for testing only)
|
/linux-4.4.14/Documentation/arm/Samsung-S3C24XX/ |
D | Suspend.txt | 59 The following is an example of code used for testing wakeup from
|
/linux-4.4.14/Documentation/s390/ |
D | DASD | 25 We performed our testing on 3380 and 3390 type disks of different
|
D | 3270.txt | 130 Here are the testing steps in detail: 268 Happy testing! I welcome any and all comments about this document, the
|
/linux-4.4.14/sound/oss/ |
D | CHANGELOG | 214 - Huge amount of testing (more testing is still required). 215 - mmap() support (works with some cards). Requires much more testing.
|
/linux-4.4.14/Documentation/input/ |
D | joystick.txt | 56 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
|
D | ntrig.txt | 116 The N-Trig windows tools provide calibration and testing routines. Also an
|
/linux-4.4.14/fs/nfsd/ |
D | Kconfig | 115 testing error recovery on the NFS client.
|
/linux-4.4.14/arch/mn10300/ |
D | Kconfig.debug | 30 for kernel debugging, non-intrusive instrumentation and testing.
|
/linux-4.4.14/Documentation/firmware_class/ |
D | README | 87 for testing and completeness, they are not called in normal use.
|
/linux-4.4.14/tools/power/cpupower/bench/ |
D | README-BENCH | 13 - Possibly Real time priority testing? -> what happens if there are
|
/linux-4.4.14/drivers/md/ |
D | Kconfig | 166 features and more testing. 175 read or write errors. It is useful for testing. 425 them to different devices. Useful for testing.
|
/linux-4.4.14/Documentation/video4linux/ |
D | si476x.txt | 19 useful for EoL testing/RF performance estimation, parameters that have
|
D | vivid.txt | 7 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 1011 data_offset to be non-zero, so this is a useful feature for testing applications. 1024 used for testing this API. Whether this API should be used for new drivers is 1118 - Some support for testing compressed video 1123 - Add ARGB888 overlay support: better testing of the alpha channel
|
D | si470x.txt | 49 Testing is usually done with most application under Debian/testing:
|
D | uvcvideo.txt | 55 For applications that need to access XU controls directly, e.g. for testing
|
/linux-4.4.14/Documentation/dvb/ |
D | cards.txt | 20 - dvb_dummy_fe: for testing...
|
D | faq.txt | 15 are mainly intended for testing and to demonstrate how the
|
/linux-4.4.14/kernel/power/ |
D | Kconfig | 165 bool "Extra PM attributes in sysfs for low-level debugging/testing" 170 developer interested in debugging/testing Power Management, say "no".
|
/linux-4.4.14/arch/alpha/lib/ |
D | stxcpy.S | 148 cmpbge zero, t2, t8 # e0 : testing eos
|
D | ev6-stxcpy.S | 171 cmpbge zero, t2, t8 # E : testing eos (stall)
|
/linux-4.4.14/drivers/net/wireless/iwlwifi/ |
D | Kconfig | 140 Enable use of experimental ucode for testing and debugging.
|
/linux-4.4.14/drivers/isdn/i4l/ |
D | Kconfig | 97 testing of linklevel features or configuration without getting
|
/linux-4.4.14/fs/jffs2/ |
D | Kconfig | 21 testing and debugging, it's advisable to set it to one. This will
|
/linux-4.4.14/Documentation/locking/ |
D | locktorture.txt | 71 This capability is useful for automated testing.
|
/linux-4.4.14/Documentation/power/regulator/ |
D | overview.txt | 171 See Documentation/ABI/testing/sysfs-class-regulator
|
/linux-4.4.14/net/ |
D | Kconfig | 300 menu "Network testing" 308 stress testing and performance analysis. If you don't understand
|
/linux-4.4.14/Documentation/aoe/ |
D | aoe.txt | 129 is supported for testing purposes and makes the aoe driver keep
|
/linux-4.4.14/arch/m68k/q40/ |
D | README | 70 for first testing. The Q40 does not support DMA and may have trouble with
|
/linux-4.4.14/Documentation/cris/ |
D | README | 100 POSIX conformance testing by UNIFIX
|
/linux-4.4.14/drivers/firmware/ |
D | Kconfig | 59 See also Documentation/ABI/testing/sysfs-firmware-memmap.
|
/linux-4.4.14/fs/befs/ |
D | ChangeLog | 207 testing purposes. (fs/Config.in) 217 I've done some serious testing on it now (on my box anyhow), and it
|
/linux-4.4.14/Documentation/acpi/apei/ |
D | einj.txt | 5 for debugging and testing APEI and RAS features in general.
|
/linux-4.4.14/sound/drivers/ |
D | Kconfig | 72 You don't need this unless you're testing the hardware support
|
/linux-4.4.14/arch/m68k/fpsp040/ |
D | skeleton.S | 48 | The following counters are used for standalone testing
|
/linux-4.4.14/drivers/staging/speakup/ |
D | Kconfig | 189 tristate "Dummy synthesizer driver (for testing)"
|
/linux-4.4.14/drivers/usb/host/ |
D | Kconfig | 652 the PCCARD. A rather pointless thing to do, but useful for testing. 781 or embedded hosts that need to undergo USB-IF compliance testing with 782 the aid of special testing hardware. In the future, this may expand
|
/linux-4.4.14/Documentation/scheduler/ |
D | sched-deadline.txt | 124 * to come back here and continue reading (once the urge for testing is 482 The first testing application is called rt-app and can be used to 510 The second testing application is a modification of schedtool, called
|
/linux-4.4.14/net/mac80211/ |
D | Kconfig | 316 Setting this option to a low value (e.g. 4) allows testing the
|
/linux-4.4.14/Documentation/blockdev/ |
D | zram.txt | 158 read Documentation/ABI/testing/sysfs-block-zram.
|
/linux-4.4.14/ |
D | Makefile | 1079 $(Q)$(MAKE) -C tools/testing/selftests run_tests 1082 $(Q)$(MAKE) -C tools/testing/selftests clean
|
/linux-4.4.14/Documentation/serial/ |
D | moxa-smartio | 70 - 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.4.14/drivers/platform/x86/ |
D | Kconfig | 572 <file:Documentation/ABI/testing/sysfs-platform-asus-wmi> 585 <file:Documentation/ABI/testing/sysfs-platform-asus-wmi> 857 <file:Documentation/ABI/testing/sysfs-platform-samsung-laptop>
|
/linux-4.4.14/arch/microblaze/boot/dts/ |
D | system.dts | 36 model = "testing";
|
/linux-4.4.14/arch/powerpc/boot/dts/ |
D | virtex440-ml507.dts | 28 model = "testing";
|
/linux-4.4.14/drivers/mtd/devices/ |
D | Kconfig | 152 testing stuff.
|
/linux-4.4.14/arch/xtensa/configs/ |
D | common_defconfig | 278 # Network testing
|
/linux-4.4.14/Documentation/filesystems/nfs/ |
D | nfs-rdma.txt | 27 In our testing, we have obtained excellent performance results (full 10Gbit
|
/linux-4.4.14/Documentation/arm64/ |
D | acpi_object_usage.txt | 84 This table is very useful for testing platform response to error 88 and executed with the ACPICA tools only during testing.
|
/linux-4.4.14/kernel/trace/ |
D | Kconfig | 510 This option will also enable testing every syscall event. 535 This is a dumb module for testing mmiotrace. It is very dangerous
|
/linux-4.4.14/init/ |
D | Kconfig | 551 This option stands for testing when an arch implements the 581 systems, but if you are stress-testing the RCU implementation 585 Select a specific number if testing RCU itself. 609 Select a specific number if testing RCU itself. 742 boot time, for example, to allow testing of different no-CBs 757 is to ensure that randconfig testing covers mixed systems.
|
/linux-4.4.14/drivers/input/serio/ |
D | Kconfig | 151 more testing.
|
/linux-4.4.14/Documentation/virtual/kvm/ |
D | msr.txt | 261 in the window between guest testing it to detect
|