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
105 Build the system and dump-capture kernels
109 1) Build a separate custom dump-capture kernel for capturing the
112 2) Or use the system kernel binary itself as dump-capture kernel and there is
113    no need to build a separate dump-capture kernel. This is possible
120 at the same time one might want to build a custom dump capture kernel
124 dump-capture kernels for enabling kdump support.
153 Dump-capture kernel config options (Arch Independent)
166 Dump-capture kernel config options (Arch Dependent, i386 and x86_64)
182    when loading the dump-capture kernel, see section "Load the Dump-capture
199    kexec boot loader will load it in memory region reserved for dump-capture
204    start of memory region reserved for dump-capture kernel.
211 Dump-capture kernel config options (Arch Dependent, ppc64)
224 Dump-capture kernel config options (Arch Dependent, ia64)
227 - No specific options are required to create a dump-capture kernel
230   as a dump-capture kernel if desired.
244 Dump-capture kernel config options (Arch Dependent, arm)
292    where Y specifies how much memory to reserve for the dump-capture kernel
295    starting at physical address 0x01000000 (16MB) for the dump-capture kernel.
303    dump-capture kernel config option notes above.
312    any space below the alignment point may be overwritten by the dump-capture kernel,
316 Load the Dump-capture Kernel
319 After booting to the system kernel, dump-capture kernel needs to be
324 of dump-capture kernel. Following is the summary.
339 to load dump-capture kernel.
341    kexec -p <dump-capture-kernel-vmlinux-image> \
342    --initrd=<initrd-for-dump-capture-kernel> --args-linux \
346 to load dump-capture kernel.
348    kexec -p <dump-capture-kernel-bzImage> \
349    --initrd=<initrd-for-dump-capture-kernel> \
353 to load dump-capture kernel.
355    kexec --type zImage -p <dump-capture-kernel-bzImage> \
356    --initrd=<initrd-for-dump-capture-kernel> \
357    --dtb=<dtb-for-dump-capture-kernel> \
366 loading dump-capture kernel.
380 Notes on loading the dump-capture kernel:
392   due to shared interrupts in the dump-capture kernel.
397 * Boot parameter "1" boots the dump-capture kernel into single-user
400 * We generally don' have to bring up a SMP kernel just to capture the
401   dump. Hence generally it is useful either to build a UP dump-capture
402   kernel or specify maxcpus=1 option while loading dump-capture kernel.
421 After successfully loading the dump-capture kernel as previously
422 described, the system will reboot into the dump-capture kernel if a
429 will boot into the dump-capture kernel ( die_nmi() ).
433 the system will boot into the dump-capture kernel.
436 and the system will boot into the dump-capture kernel.
444 After the dump-capture kernel is booted, write out the dump file with