사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/mohitmishra786/low-level-dev-skills --skill linux-kernel-architecture시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Linux Kernel Architecture
Purpose
Provide a mental map of the Linux kernel: boot sequence, major subsystems, key data structures, and where to look in source — complementing skills/kernel/kernel-internals with architecture-level navigation for driver and subsystem work.
When to Use
- First time exploring
linux.gitfor a feature or bug - Understanding how boot reaches
initand driverprobe - Tracing a syscall or interrupt through subsystems
- Onboarding before
skills/kernel-dev/platform-device-modelor driver skills
Workflow
1. Boot flow (x86/ARM64 simplified)
firmware/UEFI
├── arch/*/boot — decompress kernel, early setup
├── start_kernel() — mm, scheduler, timers, IRQ subsys
├── rest_init() → kernel_init → run_init_process
└── userspace init (systemd)Driver module_init / device_initcall run during start_kernel before init.
2. Major subsystems
| Subsystem | Path (typical) | Key structs |
|---|---|---|
| Scheduler | kernel/sched/ | task_struct, sched_entity |
| Memory | mm/ | struct page, mm_struct, vm_area_struct |
| VFS | fs/ | inode, dentry, file, super_block |
| Block | block/ | request_queue, gendisk |
| Net | net/ | sk_buff, net_device |
| Drivers | drivers/ | device, device_driver |
| Syscalls | kernel/, fs/, mm/ | SYSCALL_DEFINE* |
3. Initcall levels
/* include/linux/init.h — order matters */
early_initcall → core_initcall → postcore_initcall
→ arch_initcall → subsys_initcall → fs_initcall
→ device_initcall → late_initcallPlatform drivers usually register at subsys_initcall or via module_init.
4. Finding code
# Locate symbol
grep -rn "platform_driver_register" drivers/
# Trace config
./scripts/config --state CONFIG_FOO
# File hierarchy docs
ls Documentation/admin-guide/5. Agent usage
/linux-kernel-architecture Where does page fault handling live and what calls it?Common Problems
| Symptom | Cause | Fix |
|---|---|---|
| Driver probes too early | Initcall vs DT ordering | Defer with deferred_probe |
| Symbol missing | Built as module | modprobe or built-in CONFIG_* |
| Wrong subsystem | Similar names in drivers/ | Follow struct bus_type |
| Boot hang | Early printk disabled | earlyprintk, initcall_debug |
Related Skills
skills/kernel/kernel-internals— scheduler, SLUB, VFS depthskills/kernel-dev/kernel-memory-management— mm/ detailsskills/kernel-dev/platform-device-model— driver modelskills/kernel-dev/device-tree— hardware descriptionskills/low-level-programming/linux-kernel-modules— LKM basics



