arch/powerpc/include/asm/secvar.h

File Facts

System

Linux kernel

Corpus path

arch/powerpc/include/asm/secvar.h

Extension

.h

Size

954 bytes

Lines

40

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/types.h
• linux/errno.h
• linux/sysfs.h

Detected Declarations

• struct secvar_operations
• function set_secvar_ops

Annotated Snippet

struct secvar_operations {
	int (*get)(const char *key, u64 key_len, u8 *data, u64 *data_size);
	int (*get_next)(const char *key, u64 *key_len, u64 keybufsize);
	int (*set)(const char *key, u64 key_len, u8 *data, u64 data_size);
	ssize_t (*format)(char *buf, size_t bufsize);
	int (*max_size)(u64 *max_size);

	// NULL-terminated array of fixed variable names
	// Only used if get_next() isn't provided
	const char * const *var_names;
};

#ifdef CONFIG_PPC_SECURE_BOOT

int set_secvar_ops(const struct secvar_operations *ops);

#else

static inline int set_secvar_ops(const struct secvar_operations *ops) { return 0; }

#endif

#endif

Annotation

• Immediate include surface: `linux/types.h`, `linux/errno.h`, `linux/sysfs.h`.
• Detected declarations: `struct secvar_operations`, `function set_secvar_ops`.
• Atlas domain: Architecture Layer / arch/powerpc.
• 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.