arch/sparc/kernel/windows.c

File Facts

System

Linux kernel

Corpus path

arch/sparc/kernel/windows.c

Extension

.c

Size

3407 bytes

Lines

131

Domain

Architecture Layer

Bucket

arch/sparc

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.
• Touches user memory; correctness depends on fault-safe copying and privilege boundary handling.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/kernel.h
• linux/sched.h
• linux/string.h
• linux/mm.h
• linux/smp.h
• asm/cacheflush.h
• linux/uaccess.h
• kernel.h

Detected Declarations

• function Copyright
• function shift_window_buffer
• function setup_frame
• function copy_aligned_window
• function try_to_clear_window_buffer

Annotated Snippet

sizeof(struct reg_window32))) {
			force_exit_sig(SIGILL);
			return;
		}
	}
	tp->w_saved = 0;
}

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/sched.h`, `linux/string.h`, `linux/mm.h`, `linux/smp.h`, `asm/cacheflush.h`, `linux/uaccess.h`, `kernel.h`.
• Detected declarations: `function Copyright`, `function shift_window_buffer`, `function setup_frame`, `function copy_aligned_window`, `function try_to_clear_window_buffer`.
• Atlas domain: Architecture Layer / arch/sparc.
• Implementation status: source implementation candidate.
• This snippet crosses the user/kernel memory boundary; validate fault handling and access checks before translating the pattern.

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.