| /linux/lib/kunit/ |
| H A D | try-catch-impl.h | 20 kunit_try_catch_func_t catch) in kunit_try_catch_init() argument
24 try_catch->catch = catch; in kunit_try_catch_init()
|
| H A D | try-catch.c | 75 try_catch->catch(try_catch->context); in kunit_try_catch_run()
114 try_catch->catch(try_catch->context); in kunit_try_catch_run()
|
| H A D | Makefile | 9 try-catch.o \
|
| /linux/tools/testing/kunit/test_data/ |
| H A D | test_kernel_panic_interrupt.log | 13 [ 0.060000] # Subtest: kunit-try-catch-test
17 [ 0.060000] ok 2 - kunit-try-catch-test
|
| H A D | test_config_printk_time.log | 13 [ 0.060000] # Subtest: kunit-try-catch-test
17 [ 0.060000] ok 2 - kunit-try-catch-test
|
| H A D | test_pound_sign.log | 15 [ 0.060000] # Subtest: kunit-try-catch-test
19 [ 0.060000] ok 2 - kunit-try-catch-test
|
| H A D | test_output_with_prefix_isolated_correctly.log | 14 [ 0.060000] # Subtest: kunit-try-catch-test
18 [ 0.060000] ok 2 - kunit-try-catch-test
|
| H A D | test_pound_no_prefix.log | 15 # Subtest: kunit-try-catch-test
19 ok 2 - kunit-try-catch-test
|
| H A D | test_multiple_prefixes.log | 13 [ 0.060000][ T1] # Subtest: kunit-try-catch-test
17 [ 0.060000][ T1] ok 2 - kunit-try-catch-test
|
| H A D | test_interrupted_tap_output.log | 19 [ 0.060000] # Subtest: kunit-try-catch-test
23 [ 0.060000] ok 2 - kunit-try-catch-test
|
| /linux/include/kunit/ |
| H A D | try-catch.h | 49 kunit_try_catch_func_t catch; member
|
| /linux/arch/parisc/ |
| H A D | Kconfig.debug | 9 to catch memory overwrites at runtime. For more advanced
|
| /linux/tools/testing/selftests/bpf/ |
| H A D | verify_sig_setup.sh | 84 catch() function
|
| H A D | vmtest.sh | 350 catch() function
|
| /linux/drivers/gpu/drm/i915/ |
| H A D | Kconfig.debug | 67 performance but will catch some internal issues.
160 performance but will catch some internal issues.
172 performance but will catch some internal issues.
|
| /linux/arch/xtensa/ |
| H A D | Kconfig.debug | 31 It is easy to make wrong hardware configuration, this test should catch it early.
|
| /linux/Documentation/dev-tools/ |
| H A D | ubsan.rst | 8 UBSAN uses compile-time instrumentation to catch undefined behavior (UB).
|
| /linux/drivers/gpu/drm/xe/ |
| H A D | Kconfig.debug | 27 performance but will catch some internal issues.
|
| /linux/Documentation/networking/device_drivers/ethernet/toshiba/ |
| H A D | spider_net.rst | 58 flowing, then the tail pointer can catch up to the hardware pointer.
70 RX traffic is flowing, then the head pointer can catch up to the tail
119 pointer will catch up to the head, notice the not-empty condition,
|
| /linux/Documentation/dev-tools/kunit/ |
| H A D | architecture.rst | 103 `lib/kunit/try-catch.c <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/lib…
|
| /linux/Documentation/trace/ |
| H A D | stm.rst | 70 catch-all entry "default" will be used, if it exists. This entry also
115 node, the stm core will use the catch-all entry "default", if one
|
| /linux/Documentation/arch/powerpc/ |
| H A D | kasan.txt | 23 - It would be good to support inline instrumentation so as to be able to catch
|
| /linux/Documentation/gpu/ |
| H A D | drm-usage-stats.rst | 94 implementation easier, but are required to catch up with the previously reported
115 implementation easier, but are required to catch up with the previously reported
|
| /linux/drivers/firmware/arm_scmi/ |
| H A D | Kconfig | 86 called scmi_power_control. Note this may needed early in boot to catch
|
| /linux/Documentation/PCI/ |
| H A D | acpi-info.rst | 66 bridge registers (including ECAM space) in PNP0C02 catch-all devices [6].
78 PNP0C02 "motherboard" devices are basically a catch-all. There's no
|