arch/powerpc/platforms/pseries/papr-hvpipe.h

File Facts

System

Linux kernel

Corpus path

arch/powerpc/platforms/pseries/papr-hvpipe.h

Extension

.h

Size

1055 bytes

Lines

42

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

• No C-style include directives detected by the generator.

Detected Declarations

• struct hvpipe_source_info
• struct hvpipe_event_buf
• enum hvpipe_migrate_action

Annotated Snippet

struct hvpipe_source_info {
	struct list_head list;	/* list of sources */
	u32 srcID;
	u32 hvpipe_status;
	wait_queue_head_t recv_wqh;	 /* wake up poll() waitq */
};

/*
 * Source ID Format 0xCCRRQQQQ
 * CC = indicating value is source type (ex: 0x02 for HMC)
 * RR = 0x00 (reserved)
 * QQQQ = 0x0000 – 0xFFFF indicating the source index indetifier
 */
struct hvpipe_event_buf {
	__be32	srcID;		/* Source ID */
	u8	event_type;	/* 0x01 for hvpipe message available */
				/* from specified src ID */
				/* 0x02 for loss of pipe connection */
				/* with specified src ID */
};

void hvpipe_migration_handler(int action);
#endif /* _PAPR_HVPIPE_H */

Annotation

• Detected declarations: `struct hvpipe_source_info`, `struct hvpipe_event_buf`, `enum hvpipe_migrate_action`.
• 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.