| /linux-3.4.99/fs/nilfs2/ |
| D | segbuf.h | 172 void nilfs_clear_logs(struct list_head *logs);
173 void nilfs_truncate_logs(struct list_head *logs,
175 int nilfs_write_logs(struct list_head *logs, struct the_nilfs *nilfs);
176 int nilfs_wait_on_logs(struct list_head *logs);
177 void nilfs_add_checksums_on_logs(struct list_head *logs, u32 seed);
179 static inline void nilfs_destroy_logs(struct list_head *logs) in nilfs_destroy_logs() argument
181 nilfs_truncate_logs(logs, NULL); in nilfs_destroy_logs()
|
| D | segbuf.c | 274 void nilfs_clear_logs(struct list_head *logs) in nilfs_clear_logs() argument
278 list_for_each_entry(segbuf, logs, sb_list) in nilfs_clear_logs()
282 void nilfs_truncate_logs(struct list_head *logs, in nilfs_truncate_logs() argument
287 segbuf = list_prepare_entry(last, logs, sb_list); in nilfs_truncate_logs()
288 list_for_each_entry_safe_continue(segbuf, n, logs, sb_list) { in nilfs_truncate_logs()
295 int nilfs_write_logs(struct list_head *logs, struct the_nilfs *nilfs) in nilfs_write_logs() argument
300 list_for_each_entry(segbuf, logs, sb_list) { in nilfs_write_logs()
308 int nilfs_wait_on_logs(struct list_head *logs) in nilfs_wait_on_logs() argument
313 list_for_each_entry(segbuf, logs, sb_list) { in nilfs_wait_on_logs()
326 void nilfs_add_checksums_on_logs(struct list_head *logs, u32 seed) in nilfs_add_checksums_on_logs() argument
[all …]
|
| D | segment.c | 1323 static void nilfs_free_incomplete_logs(struct list_head *logs, in nilfs_free_incomplete_logs() argument
1330 segbuf = NILFS_FIRST_SEGBUF(logs); in nilfs_free_incomplete_logs()
1347 list_for_each_entry_continue(segbuf, logs, sb_list) { in nilfs_free_incomplete_logs()
1377 static void nilfs_cancel_segusage(struct list_head *logs, struct inode *sufile) in nilfs_cancel_segusage() argument
1382 segbuf = NILFS_FIRST_SEGBUF(logs); in nilfs_cancel_segusage()
1388 list_for_each_entry_continue(segbuf, logs, sb_list) { in nilfs_cancel_segusage()
1670 static void nilfs_abort_logs(struct list_head *logs, int err) in nilfs_abort_logs() argument
1676 if (list_empty(logs)) in nilfs_abort_logs()
1679 list_for_each_entry(segbuf, logs, sb_list) { in nilfs_abort_logs()
1715 LIST_HEAD(logs); in nilfs_segctor_abort_construction()
[all …]
|
| /linux-3.4.99/drivers/media/video/tlg2300/ |
| D | pd-video.c | 148 logs(front); in vidioc_querycap()
722 logs(front); in vidioc_g_fmt()
791 logs(front); in vidioc_s_fmt()
832 logs(front); in vidioc_g_fmt_vbi()
884 logs(front); in vidioc_s_std()
905 logs(front); in vidioc_enum_input()
915 logs(front); in vidioc_g_input()
1083 logs(front); in vidioc_g_tuner()
1111 logs(front); in vidioc_s_tuner()
1157 logs(front); in vidioc_s_frequency()
[all …]
|
| D | pd-common.h | 272 #define logs(f) do { \ macro
|
| /linux-3.4.99/Documentation/filesystems/ |
| D | nilfs2.txt | 121 of logs. Each log is composed of summary information blocks, payload
161 The logs include regular files, directory files, symbolic link files
173 The following figure shows a typical organization of the logs:
181 into multiple logs. The sequence of logs that should be treated as
|
| D | xfs.txt | 104 Valid sizes for version 1 and version 2 logs are 16384 (16k) and
105 32768 (32k). Valid sizes for version 2 logs also include
|
| /linux-3.4.99/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).
390 Views to the debug logs can be investigated through reading the corresponding
460 's390dbf' to display all the debug logs. With this tool it will be possible
461 to investigate the debug logs on a live system and with a memory dump after
466 One last possibility to investigate the debug logs at a live
469 It is possible to find the anker of the debug-logs through
474 a global variable with the pointer to the debug-logs. Following
[all …]
|
| /linux-3.4.99/drivers/net/wireless/zd1211rw/ |
| D | Kconfig | 17 messages being saved to your kernel logs, which may help debug any
|
| /linux-3.4.99/security/tomoyo/ |
| D | Kconfig | 35 audit logs that the kernel can hold on memory.
37 If you don't need audit logs, you may set this value to 0.
|
| /linux-3.4.99/Documentation/ |
| D | debugging-modules.txt | 10 In the past a debugging message which would fill people's logs was
|
| D | ramoops.txt | 10 Ramoops is an oops/panic logger that writes its logs to RAM before the system
|
| D | debugging-via-ohci1394.txt | 31 this facility proved most useful for examining long debugs logs in the printk
95 Load the ohci1394 or the fw-ohci module and check your kernel logs.
|
| /linux-3.4.99/Documentation/watchdog/ |
| D | wdt.txt | 21 The third interface logs kernel messages on additional alert events.
|
| D | hpwdt.txt | 47 confused" message in the logs or if the system gets into a hung state, then
|
| /linux-3.4.99/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-3.4.99/Documentation/i2c/ |
| D | i2c-stub | 15 arrays in memory. It will also spam the kernel logs for every command it
|
| /linux-3.4.99/Documentation/laptops/ |
| D | sony-laptop.txt | 15 subsystem. See the logs of acpid or /proc/acpi/event and
93 In your kernel logs you will find the list of all ACPI methods
|
| /linux-3.4.99/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.
|
| D | vxge.txt | 99 the statistics, register dumps using ethool, relevant logs and email them to
|
| D | generic-hdlc.txt | 123 "private" command to see port's packet descriptor rings (in kernel logs):
|
| /linux-3.4.99/Documentation/dvb/ |
| D | bt8xx.txt | 56 In your logs see f. ex.: dst_get_device_id: Recognize [DSTMCI].
|
| /linux-3.4.99/Documentation/isdn/ |
| D | README.gigaset | 412 for his work and logs to get unimodem mode working
414 for his logs and patches to get cx 100 working
420 and all the other people who sent logs and other information.
|
| /linux-3.4.99/Documentation/PCI/ |
| D | pcieaer-howto.txt | 113 internally processes and logs the error message in its PCI Express
173 correctable error status register accordingly and logs these errors.
|
| /linux-3.4.99/Documentation/x86/x86_64/ |
| D | boot-options.txt | 19 error logs.
21 Don't make logs for corrected errors. All events reported
|