/Linux-v4.19/fs/nilfs2/ |
D | segbuf.h | 160 void nilfs_clear_logs(struct list_head *logs); 161 void nilfs_truncate_logs(struct list_head *logs, 163 int nilfs_write_logs(struct list_head *logs, struct the_nilfs *nilfs); 164 int nilfs_wait_on_logs(struct list_head *logs); 165 void nilfs_add_checksums_on_logs(struct list_head *logs, u32 seed); 167 static inline void nilfs_destroy_logs(struct list_head *logs) in nilfs_destroy_logs() argument 169 nilfs_truncate_logs(logs, NULL); in nilfs_destroy_logs()
|
D | segbuf.c | 261 void nilfs_clear_logs(struct list_head *logs) in nilfs_clear_logs() argument 265 list_for_each_entry(segbuf, logs, sb_list) in nilfs_clear_logs() 269 void nilfs_truncate_logs(struct list_head *logs, in nilfs_truncate_logs() argument 274 segbuf = list_prepare_entry(last, logs, sb_list); in nilfs_truncate_logs() 275 list_for_each_entry_safe_continue(segbuf, n, logs, sb_list) { in nilfs_truncate_logs() 282 int nilfs_write_logs(struct list_head *logs, struct the_nilfs *nilfs) in nilfs_write_logs() argument 287 list_for_each_entry(segbuf, logs, sb_list) { in nilfs_write_logs() 295 int nilfs_wait_on_logs(struct list_head *logs) in nilfs_wait_on_logs() argument 300 list_for_each_entry(segbuf, logs, sb_list) { in nilfs_wait_on_logs() 313 void nilfs_add_checksums_on_logs(struct list_head *logs, u32 seed) in nilfs_add_checksums_on_logs() argument [all …]
|
D | segment.c | 1389 static void nilfs_free_incomplete_logs(struct list_head *logs, in nilfs_free_incomplete_logs() argument 1396 segbuf = NILFS_FIRST_SEGBUF(logs); in nilfs_free_incomplete_logs() 1415 list_for_each_entry_continue(segbuf, logs, sb_list) { in nilfs_free_incomplete_logs() 1445 static void nilfs_cancel_segusage(struct list_head *logs, struct inode *sufile) in nilfs_cancel_segusage() argument 1450 segbuf = NILFS_FIRST_SEGBUF(logs); in nilfs_cancel_segusage() 1456 list_for_each_entry_continue(segbuf, logs, sb_list) { in nilfs_cancel_segusage() 1740 static void nilfs_abort_logs(struct list_head *logs, int err) in nilfs_abort_logs() argument 1746 if (list_empty(logs)) in nilfs_abort_logs() 1749 list_for_each_entry(segbuf, logs, sb_list) { in nilfs_abort_logs() 1784 LIST_HEAD(logs); in nilfs_segctor_abort_construction() [all …]
|
/Linux-v4.19/Documentation/acpi/ |
D | method-tracing.txt | 29 logs when the control method evaluation is started, and disable the 34 a. Filter out the debug layer/level matched logs when control methods 40 b. Filter out the debug layer/level matched logs when the specified 47 c. Filter out the debug layer/level matched logs when the specified 84 that, as the "AML tracer" logs are implemented via ACPI_DEBUG_PRINT() 86 "AML tracer" logs. 90 a. Filter out the method start/stop "AML tracer" logs when control 103 c. Filter out the method start/stop "AML tracer" logs when the specified 143 used to match all "AML tracer" logs. 148 debug_level used to match all "AML tracer" logs.
|
/Linux-v4.19/tools/testing/selftests/rcutorture/bin/ |
D | kvm-find-errors.sh | 39 echo Build-only run, no console logs to check. 55 echo No errors in console logs.
|
/Linux-v4.19/tools/testing/selftests/ftrace/ |
D | .gitignore | 1 logs
|
D | Makefile | 6 EXTRA_CLEAN := $(OUTPUT)/logs/*
|
D | ftracetest | 115 LOG_DIR=$TOP_DIR/logs/`date +%Y%m%d-%H%M%S`/
|
/Linux-v4.19/tools/testing/selftests/pstore/ |
D | .gitignore | 1 logs
|
D | Makefile | 9 EXTRA_CLEAN := logs/* *uuid
|
D | common_tests | 60 LOG_DIR=$TOP_DIR/logs/`date +%Y%m%d-%H%M%S`_${UUID}/
|
/Linux-v4.19/drivers/media/dvb-core/ |
D | Kconfig | 39 Should not be enabled on normal cases, as logs can 52 Should not be enabled on normal cases, as logs can
|
/Linux-v4.19/arch/arm/boot/dts/ |
D | at91-wb45n.dtsi | 114 logs@7fa0000 { 115 label = "logs";
|
/Linux-v4.19/Documentation/s390/ |
D | s390dbf.txt | 12 One purpose of this is to inspect the debug logs after a production system crash 15 it is possible to look at the debug logs on a live system via the Linux 54 The debug logs can be inspected in a live system through entries in 68 All debug logs have an actual debug level (range from 0 to 6). 401 Views to the debug logs can be investigated through reading the corresponding 471 's390dbf' to display all the debug logs. With this tool it will be possible 472 to investigate the debug logs on a live system and with a memory dump after 477 One last possibility to investigate the debug logs at a live 480 It is possible to find the anker of the debug-logs through 485 a global variable with the pointer to the debug-logs. Following [all …]
|
/Linux-v4.19/security/tomoyo/ |
D | Kconfig | 37 audit logs that the kernel can hold on memory. 39 If you don't need audit logs, you may set this value to 0.
|
/Linux-v4.19/drivers/net/wireless/zydas/zd1211rw/ |
D | Kconfig | 17 messages being saved to your kernel logs, which may help debug any
|
/Linux-v4.19/Documentation/filesystems/ |
D | nilfs2.txt | 183 of logs. Each log is composed of summary information blocks, payload 223 The logs include regular files, directory files, symbolic link files 235 The following figure shows a typical organization of the logs: 243 into multiple logs. The sequence of logs that should be treated as
|
/Linux-v4.19/Documentation/ |
D | debugging-modules.txt | 10 In the past a debugging message which would fill people's logs was
|
D | DMA-attributes.txt | 140 to the system logs. Although this can help to identify and debug problems, 142 and can actually flood the system logs with error messages that aren't any 146 where allocation failures are not a problem, and shouldn't bother the logs.
|
D | debugging-via-ohci1394.txt | 35 this facility proved most useful for examining long debugs logs in the printk 93 Load the firewire-ohci module and check your kernel logs.
|
/Linux-v4.19/Documentation/watchdog/ |
D | wdt.txt | 21 The third interface logs kernel messages on additional alert events.
|
/Linux-v4.19/Documentation/blockdev/ |
D | README.DAC960 | 413 The following annotated logs demonstrate the controller configuration and and 418 logical drives, one RAID-5 and one RAID-6. Note that these logs are from an 453 driver logs the following console status messages indicating that Logical 505 Within 10 seconds of this command the driver logs the initiation of the 553 Finally, the rebuild completes successfully. The driver logs the status of the 585 The following annotated logs demonstrate the controller configuration and and 590 logical drives, one RAID-5 and one RAID-6. Note that these logs are from an 625 driver logs the following console status messages: 688 Finally, the rebuild completes successfully. The driver logs the status of the 736 the console by the driver. Within 60 seconds of this command the driver logs:
|
/Linux-v4.19/Documentation/laptops/ |
D | sony-laptop.txt | 15 subsystem. See the logs of /proc/bus/input/devices to find out what those 93 In your kernel logs you will find the list of all ACPI methods
|
/Linux-v4.19/Documentation/networking/ |
D | vortex.txt | 86 of output in your system logs. debug=1 is default. 405 o Any kernel logs which are produced. The more the merrier. 411 To ensure that all kernel logs are available, add the 432 send all logs to the maintainer.
|
/Linux-v4.19/Documentation/i2c/ |
D | i2c-stub | 15 arrays in memory. It will also spam the kernel logs for every command it
|