Home
last modified time | relevance | path

Searched refs:relocated (Results 1 – 10 of 10) sorted by relevance

/linux/arch/s390/boot/
H A Dhead_kdump.S17 # kdump entry (new kernel - not yet relocated)
29 lg %r2,0(%r2) # already relocated:
77 basr %r14,%r14 # Start relocated kernel
83 # Startup of kdump (relocated new kernel)
/linux/fs/isofs/
H A Disofs.h115 extern int parse_rock_ridge_inode(struct iso_directory_record *, struct inode *, int relocated);
132 int relocated);
/linux/arch/powerpc/kvm/
H A Dbook3s.c456 int relocated = (kvmppc_get_msr(vcpu) & (data ? MSR_DR : MSR_IR)); in kvmppc_xlate() local
459 if (relocated) { in kvmppc_xlate()
/linux/Documentation/bpf/
H A Dsigning.rst48 So a signature over the original instructions cannot match the relocated
49 instructions the verifier ends up checking, and the relocated form cannot be
100 The kernel never has to verify the relocated target programs: it verifies the
H A Dllvm_reloc.rst118 The actual to-be-relocated data (0 or section offset)
126 The actual to-be-relocated data is stored at ``r_offset`` and the read/write data
/linux/Documentation/arch/riscv/
H A Dboot.rst161 is only relocated virtually.
/linux/Documentation/admin-guide/hw-vuln/
H A Dindirect-target-selection.rst158 relocated to safe thunks.
/linux/arch/arm/boot/compressed/
H A Dhead.S533 mov r0, r9 @ start of relocated zImage
534 add r1, sp, r6 @ end of relocated zImage
/linux/Documentation/bpf/libbpf/
H A Dlibbpf_overview.rst196 about the field that should be relocated on the target kernel. i.e, if the
/linux/Documentation/arch/x86/
H A Dboot.rst120 When using bzImage, the protected-mode kernel was relocated to
1094 relocated to 0x90000. For the "old" protocol, the
1321 (relocated, if appropriate.)