document differences in kexec and Linux boot flows between architectures
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 300
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
Description
First code is often: `arch/$ARCH/kernel/head.S`
## x86
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/x86/kernel/machine_kexec_64.c?h=v6.15-rc6#n53
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/x86/kernel/x86_init.c?h=v6.15-rc6#n123
## arm
has no `kexec_file_load` yet, WIP was there
https://lore.kernel.org/linux-arm-kernel/20200601204127.GS1551@shell.armlinux.org.uk/
## arm64
tbd
## riscv
tbd
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with arch/$ARCH/kernel/head.S and the linked x86 machine_kexec_64.c and x86_init.c references. Review the arm kexec_file_load discussion, then investigate the arm64 and riscv flows. Done means the book documents the kexec and Linux boot-flow differences across x86, arm, arm64, and riscv.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- documentation, operating-systems
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100