arch/alpha/lib/ev6-clear_page.S

Source file repositories/reference/linux-study-clean/arch/alpha/lib/ev6-clear_page.S

File Facts

System: Linux kernel
Corpus path: arch/alpha/lib/ev6-clear_page.S
Extension: .S
Size: 693 bytes
Lines: 57
Domain: Architecture Layer
Bucket: arch/alpha
Inferred role: Architecture Layer: exported/initcall integration point
Status: integration 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.
Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.

Dependency Surface

linux/export.h

Detected Declarations

export clear_page

Annotated Snippet

#include <linux/export.h>
        .text
        .align 4
        .global clear_page
        .ent clear_page
clear_page:
        .prologue 0

	lda	$0,128
	lda	$1,125
	addq	$16,64,$2
	addq	$16,128,$3

	addq	$16,192,$17
	wh64	($16)
	wh64	($2)
	wh64	($3)

1:	wh64	($17)
	stq	$31,0($16)
	subq	$0,1,$0
	subq	$1,1,$1

	stq	$31,8($16)
	stq	$31,16($16)
	addq	$17,64,$2
	nop

	stq	$31,24($16)
	stq	$31,32($16)
	cmovgt	$1,$2,$17
	nop

	stq	$31,40($16)
	stq	$31,48($16)
	nop
	nop

	stq	$31,56($16)
	addq	$16,64,$16
	nop
	bne	$0,1b

	ret
	nop
	nop
	nop

	.end clear_page
	EXPORT_SYMBOL(clear_page)

Annotation

Immediate include surface: `linux/export.h`.
Detected declarations: `export clear_page`.
Atlas domain: Architecture Layer / arch/alpha.
Implementation status: integration 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.