include/linux/arm_sdei.h

File Facts

System

Linux kernel

Corpus path

include/linux/arm_sdei.h

Extension

.h

Size

2730 bytes

Lines

87

Domain

Core OS

Bucket

Core Kernel Interface

Inferred role

Core OS: implementation source

Status

source implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• uapi/linux/arm_sdei.h
• acpi/ghes.h
• asm/sdei.h

Detected Declarations

• struct sdei_registered_event
• function sdei_mask_local_cpu
• function sdei_unmask_local_cpu
• function acpi_sdei_init

Annotated Snippet

struct sdei_registered_event {
	/* For use by arch code: */
	struct pt_regs          interrupted_regs;

	sdei_event_callback	*callback;
	void			*callback_arg;
	u32			 event_num;
	u8			 priority;
};

/* The arch code entry point should then call this when an event arrives. */
int notrace sdei_event_handler(struct pt_regs *regs,
			       struct sdei_registered_event *arg);

/* arch code may use this to retrieve the extra registers. */
int sdei_api_event_context(u32 query, u64 *result);

#endif /* __LINUX_ARM_SDEI_H */

Annotation

• Immediate include surface: `uapi/linux/arm_sdei.h`, `acpi/ghes.h`, `asm/sdei.h`.
• Detected declarations: `struct sdei_registered_event`, `function sdei_mask_local_cpu`, `function sdei_unmask_local_cpu`, `function acpi_sdei_init`.
• Atlas domain: Core OS / Core Kernel Interface.
• 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.