arch/powerpc/platforms/pseries/papr-rtas-common.h

File Facts

System

Linux kernel

Corpus path

arch/powerpc/platforms/pseries/papr-rtas-common.h

Extension

.h

Size

2347 bytes

Lines

62

Domain

Architecture Layer

Bucket

arch/powerpc

Inferred role

Architecture Layer: operation-table or driver-model contract

Status

pattern 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 an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/types.h

Detected Declarations

• struct papr_rtas_blob
• struct papr_rtas_sequence

Annotated Snippet

const struct file_operations *fops, char *name);
extern bool papr_rtas_sequence_should_stop(const struct papr_rtas_sequence *seq,
				s32 status, bool init_state);
extern ssize_t papr_rtas_common_handle_read(struct file *file,
			char __user *buf, size_t size, loff_t *off);
extern int papr_rtas_common_handle_release(struct inode *inode,
					struct file *file);
extern loff_t papr_rtas_common_handle_seek(struct file *file, loff_t off,
					int whence);
#endif /* _ASM_POWERPC_PAPR_RTAS_COMMON_H */

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct papr_rtas_blob`, `struct papr_rtas_sequence`.
• Atlas domain: Architecture Layer / arch/powerpc.
• Implementation status: pattern 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.