include/linux/vt_buffer.h
Source file repositories/reference/linux-study-clean/include/linux/vt_buffer.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/vt_buffer.h- Extension
.h- Size
- 1127 bytes
- Lines
- 50
- Domain
- Core OS
- Bucket
- Core Kernel Interface
- Inferred role
- Core OS: implementation source
- Status
- source implementation candidate
Why This File Exists
Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
Dependency Surface
linux/string.hasm/vga.h
Detected Declarations
function scr_memsetwfunction scr_memcpywfunction scr_memmovew
Annotated Snippet
#ifndef _LINUX_VT_BUFFER_H_
#define _LINUX_VT_BUFFER_H_
#include <linux/string.h>
#if IS_ENABLED(CONFIG_VGA_CONSOLE)
#include <asm/vga.h>
#endif
#ifndef VT_BUF_HAVE_RW
#define scr_writew(val, addr) (*(addr) = (val))
#define scr_readw(addr) (*(addr))
#endif
#ifndef VT_BUF_HAVE_MEMSETW
static inline void scr_memsetw(u16 *s, u16 c, unsigned int count)
{
memset16(s, c, count / 2);
}
#endif
#ifndef VT_BUF_HAVE_MEMCPYW
static inline void scr_memcpyw(u16 *d, const u16 *s, unsigned int count)
{
memcpy(d, s, count);
}
#endif
#ifndef VT_BUF_HAVE_MEMMOVEW
static inline void scr_memmovew(u16 *d, const u16 *s, unsigned int count)
{
memmove(d, s, count);
}
#endif
#endif
Annotation
- Immediate include surface: `linux/string.h`, `asm/vga.h`.
- Detected declarations: `function scr_memsetw`, `function scr_memcpyw`, `function scr_memmovew`.
- Atlas domain: Core OS / Core Kernel Interface.
- 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.