Lines Matching full: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
47 passed to the dump-capture kernel through the elfcorehdr= boot
51 With the dump-capture kernel, you can access the memory image through
106 Build the system and dump-capture kernels
110 1) Build a separate custom dump-capture kernel for capturing the
113 2) Or use the system kernel binary itself as dump-capture kernel and there is
114    no need to build a separate dump-capture kernel. This is possible
121 at the same time one might want to build a custom dump capture kernel
125 dump-capture kernels for enabling kdump support.
159 Dump-capture kernel config options (Arch Independent)
177 Dump-capture kernel config options (Arch Dependent, i386 and x86_64)
186    command line when loading the dump-capture kernel because one
208    kexec boot loader will load it in memory region reserved for dump-capture
213    start of memory region reserved for dump-capture kernel.
220 Dump-capture kernel config options (Arch Dependent, ppc64)
233 Dump-capture kernel config options (Arch Dependent, arm)
241 Dump-capture kernel config options (Arch Dependent, arm64)
244 - Please note that kvm of the dump-capture kernel will not be enabled
252    Here 'size' specifies how much memory to reserve for the dump-capture kernel
255    starting at physical address 0x01000000 (16MB) for the dump-capture kernel.
338 Load the Dump-capture Kernel
341 After booting to the system kernel, dump-capture kernel needs to be
346 of dump-capture kernel. Following is the summary.
370 to load dump-capture kernel::
372    kexec -p <dump-capture-kernel-vmlinux-image> \
373    --initrd=<initrd-for-dump-capture-kernel> --args-linux \
377 to load dump-capture kernel::
379    kexec -p <dump-capture-kernel-bzImage> \
380    --initrd=<initrd-for-dump-capture-kernel> \
384 to load dump-capture kernel::
386    kexec --type zImage -p <dump-capture-kernel-bzImage> \
387    --initrd=<initrd-for-dump-capture-kernel> \
388    --dtb=<dtb-for-dump-capture-kernel> \
392 to load dump-capture kernel::
394    kexec -p <dump-capture-kernel-Image> \
395    --initrd=<initrd-for-dump-capture-kernel> \
399 loading dump-capture kernel.
421 Notes on loading the dump-capture kernel:
433   due to shared interrupts in the dump-capture kernel.
438 * Boot parameter "1" boots the dump-capture kernel into single-user
441 * We generally don't have to bring up a SMP kernel just to capture the
442   dump. Hence generally it is useful either to build a UP dump-capture
443   kernel or specify maxcpus=1 option while loading dump-capture kernel.
447 * You should enable multi-cpu support in dump-capture kernel if you intend
451   SMP dump-capture kernel and specify maxcpus/nr_cpus options while loading it.
470 After successfully loading the dump-capture kernel as previously
471 described, the system will reboot into the dump-capture kernel if a
478 will boot into the dump-capture kernel ( die_nmi() ).
482 the system will boot into the dump-capture kernel.
485 and the system will boot into the dump-capture kernel.
493 After the dump-capture kernel is booted, write out the dump file with
577 2. Load the dump-capture kernel
579 3. After the dump-capture kerne get booted, restore the keys to user keyring