Home
last modified time | relevance | path

Searched refs:dumps (Results 1 – 25 of 51) sorted by relevance

123

/Linux-v5.4/Documentation/ABI/stable/
Dsysfs-firmware-opal-dump6 the FSP and platform dumps through OPAL firmware interface.
18 among all dumps. For determining the type
/Linux-v5.4/Documentation/features/perf/perf-stackdump/
Darch-support.txt4 # description: arch supports perf events stack dumps
/Linux-v5.4/Documentation/admin-guide/
Dramoops.rst39 variable while setting 0 in that variable dumps only the panics.
41 The module uses a counter to record multiple dumps but the counter gets reset
42 on restart (i.e. new dumps after the restart will overwrite old ones).
/Linux-v5.4/arch/x86/ras/
DKconfig23 file that dumps out the current state of all pages logged so far.
/Linux-v5.4/tools/cgroup/
Diocost_monitor.py256 output += json.dumps(iocstat.dict(now))
273 output += '\n' + json.dumps(iocg_stat.dict(now, path))
/Linux-v5.4/Documentation/fault-injection/
Dprovoke-crashes.rst6 predefined crashpoints to evaluate the reliability of crash dumps obtained
/Linux-v5.4/Documentation/ABI/testing/
Ddebugfs-cros-ec14 This file dumps the EC panic information from the previous
/Linux-v5.4/Documentation/s390/
Dzfcpdump.rst6 dumps on SCSI disks. The dump process is initiated by booting a dump tool, which
Dcommon_io.rst134 which subchannel they were called for, as well as dumps of some data
/Linux-v5.4/arch/sh/
DKconfig.debug48 bool "Show disassembly of nearby code in register dumps"
/Linux-v5.4/fs/
DKconfig.binfmt59 bool "Write ELF core dumps with partial segments"
207 This option enables support for performing core dumps. You almost
/Linux-v5.4/fs/proc/
DKconfig60 If you say Y here, the collected device dumps will be added
/Linux-v5.4/arch/arc/kernel/
Dentry.S93 ; access for say stack unwinding of modules for crash dumps
/Linux-v5.4/Documentation/usb/
Dehci.rst124 dumps the asynchronous schedule, used for control
129 dumps the periodic schedule, used for interrupt
/Linux-v5.4/Documentation/trace/
Devents.rst424 This command dumps a stacktrace in the trace buffer whenever the
427 For example, the following trigger dumps a stacktrace every time the
433 The following trigger dumps a stacktrace the first 5 times a kmalloc
/Linux-v5.4/sound/soc/sof/
DKconfig119 human-readable form instead of just 32-bit hex dumps. This is useful
/Linux-v5.4/Documentation/admin-guide/sysctl/
Dfs.rst296 pipe handler that knows to treat privileged core dumps with
297 care, or specific directory defined for catching core dumps.
/Linux-v5.4/drivers/firmware/efi/
DKconfig33 will allow writing console messages, crash dumps, or anything
/Linux-v5.4/drivers/net/wireless/marvell/libertas/
DREADME49 device. When raw is enabled, then it dumps the raw EEPROM data
/Linux-v5.4/Documentation/admin-guide/kdump/
Dkdump.rst155 1) Enable "kernel crash dumps" support under "Processor type and
195 "kernel crash dumps" is enabled. A suitable value depends upon
/Linux-v5.4/Documentation/
DChanges158 that it produces readable dumps that can be used as-is (this also
/Linux-v5.4/Documentation/process/
Dchanges.rst158 that it produces readable dumps that can be used as-is (this also
/Linux-v5.4/Documentation/ia64/
Dmca.rst186 the previous task. You can look at that field in dumps or debuggers.
/Linux-v5.4/tools/perf/Documentation/
Dperf-trace.txt225 dumps just boolean map values and integer keys, in time this will print in hex
/Linux-v5.4/arch/ia64/
DKconfig432 bool "kernel crash dumps"

123