arch/um/kernel/early_printk.c
Source file repositories/reference/linux-study-clean/arch/um/kernel/early_printk.c
File Facts
- System
- Linux kernel
- Corpus path
arch/um/kernel/early_printk.c- Extension
.c- Size
- 663 bytes
- Lines
- 33
- Domain
- Architecture Layer
- Bucket
- arch/um
- Inferred role
- Architecture Layer: implementation source
- Status
- source implementation candidate
Why This File Exists
CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/kernel.hlinux/console.hlinux/init.hos.h
Detected Declarations
function Copyrightfunction setup_early_printk
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0-only
/*
* Copyright (C) 2011 Richard Weinberger <richrd@nod.at>
*/
#include <linux/kernel.h>
#include <linux/console.h>
#include <linux/init.h>
#include <os.h>
static void early_console_write(struct console *con, const char *s, unsigned int n)
{
um_early_printk(s, n);
}
static struct console early_console_dev = {
.name = "earlycon",
.write = early_console_write,
.flags = CON_BOOT,
.index = -1,
};
static int __init setup_early_printk(char *buf)
{
if (!early_console) {
early_console = &early_console_dev;
register_console(&early_console_dev);
}
return 0;
}
early_param("earlyprintk", setup_early_printk);
Annotation
- Immediate include surface: `linux/kernel.h`, `linux/console.h`, `linux/init.h`, `os.h`.
- Detected declarations: `function Copyright`, `function setup_early_printk`.
- Atlas domain: Architecture Layer / arch/um.
- Implementation status: source implementation candidate.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.