arch/powerpc/platforms/cell/spufs/fault.c

File Facts

System

Linux kernel

Corpus path

arch/powerpc/platforms/cell/spufs/fault.c

Extension

.c

Size

4373 bytes

Lines

168

Domain

Architecture Layer

Bucket

arch/powerpc

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/sched/signal.h
• linux/mm.h
• asm/spu.h
• asm/spu_csa.h
• spufs.h

Detected Declarations

• function spufs_handle_event
• function spufs_handle_class0
• function spufs_handle_class1

Annotated Snippet

if (ctx->state == SPU_STATE_RUNNABLE) {
			if (flt & VM_FAULT_MAJOR)
				ctx->spu->stats.maj_flt++;
			else
				ctx->spu->stats.min_flt++;
		}

		if (ctx->spu)
			ctx->ops->restart_dma(ctx);
	} else
		spufs_handle_event(ctx, ea, SPE_EVENT_SPE_DATA_STORAGE);

	spuctx_switch_state(ctx, SPU_UTIL_SYSTEM);
	return ret;
}

Annotation

• Immediate include surface: `linux/sched/signal.h`, `linux/mm.h`, `asm/spu.h`, `asm/spu_csa.h`, `spufs.h`.
• Detected declarations: `function spufs_handle_event`, `function spufs_handle_class0`, `function spufs_handle_class1`.
• Atlas domain: Architecture Layer / arch/powerpc.
• Implementation status: source implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.