Lines Matching refs:capture

11 Kdump uses kexec to quickly boot to a dump-capture kernel whenever a
14 the reboot and is accessible to the dump-capture kernel.
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
31 region just before rebooting into the dump-capture kernel.
45 passed to the dump-capture kernel through the elfcorehdr= boot
50 With the dump-capture kernel, you can access the memory image through
104 Build the system and dump-capture kernels
108 1) Build a separate custom dump-capture kernel for capturing the
111 2) Or use the system kernel binary itself as dump-capture kernel and there is
112    no need to build a separate dump-capture kernel. This is possible
119 at the same time one might want to build a custom dump capture kernel
123 dump-capture kernels for enabling kdump support.
152 Dump-capture kernel config options (Arch Independent)
166 Dump-capture kernel config options (Arch Dependent, i386 and x86_64)
184    when loading the dump-capture kernel, see section "Load the Dump-capture
201    kexec boot loader will load it in memory region reserved for dump-capture
206    start of memory region reserved for dump-capture kernel.
213 Dump-capture kernel config options (Arch Dependent, ppc64)
226 Dump-capture kernel config options (Arch Dependent, ia64)
229 - No specific options are required to create a dump-capture kernel
232   as a dump-capture kernel if desired.
248 Dump-capture kernel config options (Arch Dependent, arm)
256 Dump-capture kernel config options (Arch Dependent, arm64)
259 - Please note that kvm of the dump-capture kernel will not be enabled
297    where Y specifies how much memory to reserve for the dump-capture kernel
300    starting at physical address 0x01000000 (16MB) for the dump-capture kernel.
308    dump-capture kernel config option notes above.
322 Load the Dump-capture Kernel
325 After booting to the system kernel, dump-capture kernel needs to be
330 of dump-capture kernel. Following is the summary.
358 to load dump-capture kernel::
360    kexec -p <dump-capture-kernel-vmlinux-image> \
361    --initrd=<initrd-for-dump-capture-kernel> --args-linux \
365 to load dump-capture kernel::
367    kexec -p <dump-capture-kernel-bzImage> \
368    --initrd=<initrd-for-dump-capture-kernel> \
372 to load dump-capture kernel::
374    kexec --type zImage -p <dump-capture-kernel-bzImage> \
375    --initrd=<initrd-for-dump-capture-kernel> \
376    --dtb=<dtb-for-dump-capture-kernel> \
380 to load dump-capture kernel::
382    kexec -p <dump-capture-kernel-Image> \
383    --initrd=<initrd-for-dump-capture-kernel> \
391 loading dump-capture kernel.
413 Notes on loading the dump-capture kernel:
425   due to shared interrupts in the dump-capture kernel.
430 * Boot parameter "1" boots the dump-capture kernel into single-user
433 * We generally don't have to bring up a SMP kernel just to capture the
434   dump. Hence generally it is useful either to build a UP dump-capture
435   kernel or specify maxcpus=1 option while loading dump-capture kernel.
439 * You should enable multi-cpu support in dump-capture kernel if you intend
443   SMP dump-capture kernel and specify maxcpus/nr_cpus, disable_cpu_apicid=[X]
463 After successfully loading the dump-capture kernel as previously
464 described, the system will reboot into the dump-capture kernel if a
471 will boot into the dump-capture kernel ( die_nmi() ).
475 the system will boot into the dump-capture kernel.
478 and the system will boot into the dump-capture kernel.
486 After the dump-capture kernel is booted, write out the dump file with