Searched full:dump (Results 1 – 25 of 177) sorted by relevance
12345678
| /Documentation/ABI/stable/ |
| D | sysfs-firmware-opal-dump | 1 What: /sys/firmware/opal/dump
12 we will initiate a dump.
15 0xXX-0xYYYY: A directory for dump of type 0xXX and
20 and ID of the dump, use the id and type files.
21 Do not rely on any particular size of dump
22 type or dump id.
25 Each dump has the following files:
28 id: An ASCII representation of the dump ID
31 dump in the format "0x%x %s" with the ID
32 in hex and a description of the dump type
[all …]
|
| /Documentation/arch/s390/ |
| D | zfcpdump.rst | 2 The s390 SCSI dump tool (zfcpdump)
6 dumps on SCSI disks. The dump process is initiated by booting a dump tool, which
7 has to create a dump of the current (probably crashed) Linux image. In order to
8 not overwrite memory of the crashed Linux with data of the dump tool, the
10 dump tool is loaded. There exists an SCLP hardware interface to obtain the saved
13 This zfcpdump implementation consists of a Linux dump kernel together with
14 a user space dump tool, which are loaded together into the saved memory region
17 system can then trigger a SCSI dump by booting the SCSI disk, where zfcpdump
20 The user space dump tool accesses the memory of the crashed system by means
22 memory and registers in ELF core dump format. To access the memory which has
[all …]
|
| /Documentation/admin-guide/kdump/ |
| D | kdump.rst | 11 Kdump uses kexec to quickly boot to a dump-capture kernel whenever a
12 dump of the system kernel's memory needs to be taken (for example, when
14 the reboot and is accessible to the dump-capture kernel.
17 the memory image to a dump file on the local disk, or across the network
24 the dump-capture kernel. This ensures that ongoing Direct Memory Access
25 (DMA) from the system kernel does not corrupt the dump-capture kernel.
26 The kexec -p command loads the dump-capture kernel into this reserved
47 passed to the dump-capture kernel through the elfcorehdr= boot
51 With the dump-capture kernel, you can access the memory image through
52 /proc/vmcore. This exports the dump as an ELF-format file that you can
[all …]
|
| /Documentation/arch/powerpc/ |
| D | firmware-assisted-dump.rst | 2 Firmware-Assisted Dump
7 The goal of firmware-assisted dump is to enable the dump of
12 - Firmware-Assisted Dump (FADump) infrastructure is intended to replace
13 the existing phyp assisted dump.
15 as phyp assisted dump.
16 - Unlike phyp dump, FADump exports the memory dump through /proc/vmcore
18 kdump infrastructure for dump capture and filtering.
19 - Unlike phyp dump, userspace tool does not need to refer any sysfs
21 - Unlike phyp dump, FADump allows user to release all the memory reserved
22 for dump, with a single operation of echo 1 > /sys/kernel/fadump_release_mem.
[all …]
|
| /Documentation/virt/kvm/s390/ |
| D | s390-pv-dump.rst | 16 confidentiality until the dump is in the hands of the VM owner who
19 The confidentiality of the VM dump is ensured by the Ultravisor who
26 Dump process
29 A dump is done in 3 steps:
33 This step initializes the dump process, generates cryptographic seeds
34 and extracts dump keys with which the VM dump data will be encrypted.
42 point, vector, control and tod/timers of a vcpu. The vcpu dump can
45 in the dump data. For the same reason it is very important to not only
54 read from the swap and written to the dump target without need for any
63 decrypt the vcpu and memory data and end the dump process. When this
[all …]
|
| /Documentation/networking/devlink/ |
| D | devlink-health.rst | 35 * Object dump procedures
48 * Object dump is being taken and saved at the reporter instance (as long as
49 auto-dump is set and there is no other dump which is already stored)
58 To handle devlink health diagnose and health dump requests, devlink creates a
83 * Object dump
103 - Retrieves the last stored dump. Devlink health
104 saves a single dump. If an dump is not already stored by devlink
105 for this reporter, devlink generates a new dump.
106 Dump output is defined by the reporter.
108 - Clears the last saved dump file for the specified reporter.
[all …]
|
| D | iosm.rst | 112 device (RAM dump).
130 $ devlink region dump pci/0000:02:00.0/report.json snapshot 0
136 $ devlink region dump pci/0000:02:00.0/coredump.fcd snapshot 1
142 $ devlink region dump pci/0000:02:00.0/cdd.log snapshot 2
148 $ devlink region dump pci/0000:02:00.0/eeprom.bin snapshot 3
154 $ devlink region dump pci/0000:02:00.0/bootcore_trace.bin snapshot 4
160 $ devlink region dump pci/0000:02:00.0/bootcore_prev_trace.bin snapshot 5
|
| D | mlx5.rst | 201 The fw reporter implements `diagnose` and `dump` callbacks.
203 fw core dump and storing it into the dump buffer.
213 - Read FW core dump if already stored or trigger new one::
215 $ devlink health dump show pci/0000:82:00.0 reporter fw
223 The fw fatal reporter implements `dump` and `recover` callbacks.
224 It follows fatal errors indications by CR-space dump and recover flow.
225 The CR-space dump uses vsc interface which is valid even if the FW command
238 - Read FW CR-space dump if already stored or trigger new one::
240 $ devlink health dump show pci/0000:82:00.1 reporter fw_fatal
|
| D | devlink-region.rst | 14 or dump commands. This allows future analysis on the created snapshots.
51 $ devlink region dump DEV/REGION [ snapshot SNAPSHOT_ID ]
66 # Dump a snapshot:
67 $ devlink region dump pci/0000:00:05.0/fw-health snapshot 1
|
| /Documentation/ABI/testing/ |
| D | debugfs-hisi-zip | 4 Description: Dump of compression cores related debug registers.
10 Description: Dump of decompression cores related debug registers.
42 Description: Dump of QM related debug registers.
65 Description: Dump the number of invalid interrupts for
72 Description: Dump the number of QM async event queue interrupts.
78 Description: Dump the number of interrupts for QM abnormal event.
84 Description: Dump the number of queue allocation errors.
90 Description: Dump the number of failed QM mailbox commands.
96 Description: Dump the status of the QM.
110 Description: Dump the state of the device.
[all …]
|
| D | debugfs-hisi-sec | 30 Description: Dump of QM related debug registers.
52 Description: Dump the number of invalid interrupts for
59 Description: Dump the number of QM async event queue interrupts.
65 Description: Dump the number of interrupts for QM abnormal event.
71 Description: Dump the number of queue allocation errors.
77 Description: Dump the number of failed QM mailbox commands.
83 Description: Dump the status of the QM.
97 Description: Dump the state of the device.
111 Description: Dump the stop queue status of the QM. The default value is 0,
126 Description: Dump the total number of sent requests.
[all …]
|
| D | debugfs-hisi-hpre | 4 Description: Dump debug registers from the HPRE cluster.
43 Description: Dump debug registers from the HPRE.
49 Description: Dump debug registers from the QM.
72 Description: Dump the number of invalid interrupts for
79 Description: Dump the number of QM async event queue interrupts.
85 Description: Dump the number of interrupts for QM abnormal event.
91 Description: Dump the number of queue allocation errors.
97 Description: Dump the number of failed QM mailbox commands.
103 Description: Dump the status of the QM.
117 Description: Dump the state of the device.
[all …]
|
| D | sysfs-kernel-fadump | 7 of Firmware Assisted Dump (FADump).
21 Helps to control the dump collect feature from userspace.
23 dump and 0 to disable it.
33 save the crash dump.
40 FADump to save the crash dump in bytes.
|
| D | debugfs-driver-genwqe | 4 Description: DDCB queue dump used for debugging queueing problems.
9 Description: Dump of the current error registers.
33 Description: Dump of the error registers before the last reset of
84 Description: Dump job timeout register values for PF and VFs.
90 Description: Dump queue working time register values for PF and VFs.
|
| D | debugfs-driver-habanalabs | 236 Description: Allows the root user to dump monitors status from the device's
239 monitors registers dump.
250 Description: Triggers dump of monitor data. The value to trigger the operation
251 must be 1. Triggering the monitor dump operation initiates dump of
281 Description: Gets the state dump occurring on a CS timeout or failure.
282 State dump is used for debug and is created each time in case of
284 Reading from the node returns the newest state dump available.
286 next read would return X+1-st newest state dump.
|
| /Documentation/networking/ |
| D | gen_stats.rst | 36 Export to userspace (Dump):
43 struct gnet_dump dump;
45 if (gnet_stats_start_copy(skb, TCA_STATS2, &mystruct->lock, &dump,
49 if (gnet_stats_copy_basic(&dump, &mystruct->bstats) < 0 ||
50 gnet_stats_copy_queue(&dump, &mystruct->qstats) < 0 ||
51 gnet_stats_copy_app(&dump, &xstats, sizeof(xstats)) < 0)
54 if (gnet_stats_finish_copy(&dump) < 0)
69 TCA_XSTATS, &mystruct->lock, &dump,
118 From now on, every time you dump my_rate_est_stats it will contain
|
| /Documentation/netlink/specs/ |
| D | nlctrl.yaml | 19 - cmd-cap-dump
164 name: dump
173 doc: Get / dump genetlink families
190 dump:
194 doc: Get / dump genetlink policies
196 dump:
|
| D | fou.yaml | 84 dont-validate: [ strict, dump ]
106 dont-validate: [ strict, dump ]
125 dont-validate: [ strict, dump ]
131 dump:
|
| D | ethtool.yaml | 1161 dump: *strset-get-op
1180 dump: *linkinfo-get-op
1216 dump: *linkmodes-get-op
1249 dump: *linkstate-get-op
1264 dump: *debug-get-op
1293 dump: *wol-get-op
1328 dump: *feature-get-op
1358 dump: *privflag-get-op
1401 dump: *ring-get-op
1436 dump: *channel-get-op
[all …]
|
| D | devlink.yaml | 616 name: health-reporter-dump-ts
674 name: health-reporter-dump-ts-ns
686 name: health-reporter-auto-dump
1182 name: health-reporter-dump-ts
1184 name: health-reporter-dump-ts-ns
1186 name: health-reporter-auto-dump
1236 dont-validate: [ strict, dump ]
1252 dump:
1272 dump:
1276 value: 3 # due to a bug, port dump returns DEVLINK_CMD_NEW
[all …]
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-kernel-fadump_registered | 7 Helps to control the dump collect feature from userspace.
9 dump and 0 to disable it.
|
| /Documentation/kbuild/ |
| D | gendwarfksyms.rst | 27 --dump-dies Dump DWARF DIE contents
28 --dump-die-map Print debugging information about die_map changes
29 --dump-types Dump type strings
30 --dump-versions Dump expanded type strings used for symbol versions
85 DWARF format produced by **--dump-dies**, but with type references
159 (as shown in **--dump-dies** output).
186 (as shown in **--dump-dies** output) and the name of the
211 (as shown in **--dump-dies** output) and the name of the
247 (as shown in **--dump-dies** output).
283 (as shown in **--dump-dies** output) or symbol.
|
| /Documentation/core-api/ |
| D | netlink.rst | 50 Support dump consistency
53 If iterating over objects during dump may skip over objects or repeat
54 them - make sure to report dump inconsistency with ``NLM_F_DUMP_INTR``.
72 or separately for each operation and operation type (do vs dump) - ``split``.
|
| /Documentation/admin-guide/ |
| D | ramoops.rst | 19 Ramoops uses a predefined memory area to store the dump. The start and size
39 power of two) and each kmesg dump writes a ``record_size`` chunk of
142 Dump format
145 The data dump begins with a header, currently defined as ``====`` followed by a
146 timestamp and a new line. The dump then continues with the actual data.
151 The dump data can be read from the pstore filesystem. The format for these
|
| /Documentation/devicetree/bindings/reserved-memory/ |
| D | ramoops.yaml | 46 description: maximum size in bytes of each kmsg dump
81 If present, sets maximum type of kmsg dump reasons to store.
83 See include/linux/kmsg_dump.h KMSG_DUMP_* for other kmsg dump reason values.
95 no-dump-oops:
|
12345678