Home
last modified time | relevance | path

Searched refs:initrd (Results 1 – 25 of 127) sorted by relevance

123456

/Linux-v6.1/Documentation/translations/zh_CN/admin-guide/
Dbootconfig.rst152 用引导配置引导内核有两种方法:将引导配置附加到initrd镜像或直接嵌入内核中。
154 *initrd: initial RAM disk,初始内存磁盘*
156 将引导配置附加到initrd
159 由于默认情况下引导配置文件是用initrd加载的,因此它将被添加到initrd(initramfs)
162 [initrd][bootconfig][padding][size(le32)][checksum(le32)][#BOOTCONFIG\n]
166 当引导配置被加到initrd镜像时,整个文件大小会对齐到4字节。空字符( ``\0`` )
169 Linux内核在内存中解码initrd镜像的最后部分以获取引导配置数据。由于这种“背负式”
170 的方法,只要引导加载器传递了正确的initrd文件大小,就无需更改或更新引导加载器
175 可以用它从initrd镜像中删除或追加配置文件。你可以用以下命令来构建它::
179 要向initrd镜像添加你的引导配置文件,请按如下命令操作(旧数据会自动移除)::
[all …]
/Linux-v6.1/Documentation/admin-guide/
Dinitrd.rst1 Using the initial RAM disk (initrd)
8 initrd provides the capability to load a RAM disk by the boot loader.
11 from a different device. The previous root (from initrd) is then moved
14 initrd is mainly designed to allow system startup to occur in two phases,
16 where additional modules are loaded from initrd.
18 This document gives a brief overview of the use of initrd. A more detailed
25 When using initrd, the system typically boots as follows:
28 2) the kernel converts initrd into a "normal" RAM disk and
29 frees the memory used by initrd
33 4) root device is mounted. if it is ``/dev/ram0``, the initrd image is
[all …]
Defi-stub.rst50 The "initrd=" option
54 multiple initrd files using the "initrd=" option. This is the only EFI
58 The path to the initrd file must be an absolute path from the
66 initrd-large.img
69 initrd-small.img
70 initrd-medium.img
72 to boot with the initrd-large.img file if the current working
75 fs0:\Kernels> bzImage.efi initrd=\Kernels\initrd-large.img
99 "dtb=" is processed in the same manner as the "initrd=" option that is
Dbootconfig.rst162 bootconfig to the initrd image or embedding it in the kernel itself.
167 Since the boot configuration file is loaded with initrd by default,
168 it will be added to the end of the initrd (initramfs) image file with
171 [initrd][bootconfig][padding][size(le32)][checksum(le32)][#BOOTCONFIG\n]
175 When the boot configuration is added to the initrd image, the total
180 The Linux kernel decodes the last part of the initrd image in memory to
184 loader passes the correct initrd file size. If by any chance, the boot
189 to/from initrd image. You can build it by the following command::
193 To add your boot config file to initrd image, run bootconfig as below
196 # tools/bootconfig/bootconfig -a your-config /boot/initrd.img-X.Y.Z
[all …]
/Linux-v6.1/tools/testing/selftests/rcutorture/doc/
Dinitrd.txt1 The rcutorture scripting tools automatically create an initrd containing
7 userspace environments, you might wish to press an existing initrd
12 zcat /initrd.img > /tmp/initrd.img.zcat
13 mkdir initrd
14 cd initrd
15 cpio -id < /tmp/initrd.img.zcat
16 # Manually verify that initrd contains needed binaries and libraries.
Drcu-test-image.txt1 Normally, a minimal initrd is created automatically by the rcutorture
5 $ size tools/testing/selftests/rcutorture/initrd/init
7 328 0 8 336 150 tools/testing/selftests/rcutorture/initrd/init
15 tools/testing/selftests/rcutorture/initrd
17 For example, your tools/testing/selftests/rcutorture/initrd/init might
/Linux-v6.1/arch/arm/boot/bootp/
Dinit.S24 bl move @ move the initrd
30 ldmia r13, {r5-r9} @ get size and addr of initrd
33 @ r7 = initrd start
34 @ r8 = initrd end
56 mov r5, #4 @ Size of initrd tag (4 words)
76 data: .word initrd_start @ source initrd address
77 .word initrd_phys @ destination initrd address
78 .word initrd_size @ initrd size
DMakefile33 PHONY += initrd
34 initrd: target
/Linux-v6.1/drivers/firmware/efi/libstub/
Defi-stub-helper.c641 efi_status_t efi_load_initrd_dev_path(struct linux_efi_initrd *initrd, in efi_load_initrd_dev_path() argument
660 initrd->size = 0; in efi_load_initrd_dev_path()
661 status = efi_call_proto(lf2, load_file, dp, false, &initrd->size, NULL); in efi_load_initrd_dev_path()
665 status = efi_allocate_pages(initrd->size, &initrd->base, max); in efi_load_initrd_dev_path()
669 status = efi_call_proto(lf2, load_file, dp, false, &initrd->size, in efi_load_initrd_dev_path()
670 (void *)initrd->base); in efi_load_initrd_dev_path()
672 efi_free(initrd->size, initrd->base); in efi_load_initrd_dev_path()
680 struct linux_efi_initrd *initrd, in efi_load_initrd_cmdline() argument
690 &initrd->base, &initrd->size); in efi_load_initrd_cmdline()
708 struct linux_efi_initrd initrd, *tbl; in efi_load_initrd() local
[all …]
/Linux-v6.1/arch/um/kernel/
Dinitrd.c16 static char *initrd __initdata = NULL;
23 if (!initrd) in read_initrd()
26 area = uml_load_file(initrd, &size); in read_initrd()
37 initrd = line; in uml_initrd_setup()
/Linux-v6.1/arch/powerpc/boot/
DREADME2 To extract the kernel vmlinux, System.map, .config or initrd from the zImage binary:
7 objcopy -j .kernel:initrd -O binary zImage.initrd initrd.gz
DMakefile377 initrd- := $(patsubst zImage%, zImage.initrd%, $(image-))
378 initrd-y := $(patsubst zImage%, zImage.initrd%, \
379 $(patsubst dtbImage%, dtbImage.initrd%, \
380 $(patsubst simpleImage%, simpleImage.initrd%, \
381 $(patsubst treeImage%, treeImage.initrd%, $(image-y)))))
382 initrd-y := $(filter-out $(image-y), $(initrd-y))
383 targets += $(image-y) $(initrd-y)
389 $(addprefix $(obj)/, $(initrd-y)): $(obj)/ramdisk.image.gz
394 $(obj)/zImage.initrd.%: vmlinux $(wrapperbits) FORCE
401 $(obj)/dtbImage.initrd.%: vmlinux $(wrapperbits) $(obj)/dts/%.dtb FORCE
[all …]
Dwrapper41 initrd=
108 initrd="$1"
232 isection=.kernel:initrd
279 isection=initrd
318 isection=.kernel:initrd
458 if [ -n "$initrd" ]; then
459 real_rd="$initrd"
466 if [ -z "$initrd" ]; then
487 if [ -n "$initrd" ]; then
488 addsec $tmp "$initrd" $isection
DzImage.ps3.lds.S18 .kernel:initrd : { *(.kernel:initrd) }
Dmain.c229 struct addr_range vmlinux, initrd; in start() local
255 initrd = prep_initrd(vmlinux, chosen, in start()
279 kentry((unsigned long)initrd.addr, initrd.size, in start()
DzImage.lds.S72 .kernel:initrd :
75 *(.kernel:initrd)
/Linux-v6.1/Documentation/power/
Dswsusp-dmcrypt.rst13 You did read Documentation/admin-guide/initrd.rst and know how an initrd works.
14 You know how to create or how to modify an initrd.
19 an initrd that does your current crypto setup already.
25 or an usb stick prior to resume. So you need an initrd, that sets
31 always the same major/minor within the initrd as well as
43 Prepare your boot loader to use the initrd you will create or
48 initrd=/boot/initrd.gz
52 Finally you need to create or modify your initrd. Lets assume
53 you create an initrd that reads the required dm-crypt setup
57 named "swapkey". /etc/fstab of your initrd contains something
[all …]
/Linux-v6.1/Documentation/translations/zh_CN/devicetree/
Dusage-model.rst147 时和配置数据,如内核参数字符串和initrd镜像的位置。
153 initrd-start = <0xc8000000>;
154 initrd-end = <0xc8200000>;
157 bootargs属性包含内核参数,initrd-\*属性定义initrd blob的地址和大小。注
158initrd-end是initrd映像后的第一个地址,所以这与结构体资源的通常语义不一
/Linux-v6.1/arch/parisc/kernel/
Dkexec_file.c17 unsigned long kernel_len, char *initrd, in elf_load() argument
44 if (initrd != NULL) { in elf_load()
45 kbuf.buffer = initrd; in elf_load()
/Linux-v6.1/arch/powerpc/kexec/
Delf_64.c28 unsigned long kernel_len, char *initrd, in elf64_load() argument
91 if (initrd != NULL) { in elf64_load()
92 kbuf.buffer = initrd; in elf64_load()
/Linux-v6.1/Documentation/x86/
Dmicrocode.rst25 The microcode is stored in an initrd file. During boot, it is read from
28 The format of the combined initrd image is microcode in (uncompressed)
29 cpio format followed by the (possibly compressed) initrd image. The
30 loader parses the combined initrd image during boot.
40 scans the microcode file in the initrd. If microcode matching the
48 Here's a crude example how to prepare an initrd with microcode (this is
50 initrd, so you don't really have to do it yourself. It is documented
57 echo "You need to supply an initrd file"
64 TMPDIR=/tmp/initrd
/Linux-v6.1/tools/testing/selftests/rcutorture/bin/
Dmkinitrd.sh27 mkdir -p initrd
28 cd initrd
/Linux-v6.1/arch/arm64/kernel/
Dmachine_kexec_file.c92 char *initrd, unsigned long initrd_len, in load_other_segments() argument
135 if (initrd) { in load_other_segments()
136 kbuf.buffer = initrd; in load_other_segments()
/Linux-v6.1/arch/arm/boot/dts/
Dkirkwood-iconnect.dts19 linux,initrd-start = <0x4500040>;
20 linux,initrd-end = <0x4800000>;
164 label = "initrd";
/Linux-v6.1/Documentation/admin-guide/acpi/
Dssdt-overlays.rst70 Loading ACPI SSDTs from initrd
73 This option allows loading of user defined SSDTs from initrd and it is useful
76 It works in a similar way with initrd based ACPI tables override/upgrade: SSDT
77 AML code must be placed in the first, uncompressed, initrd under the
93 # Create the uncompressed cpio archive and concatenate the original initrd
96 cat /boot/initrd >>/boot/instrumented_initrd

123456