arch/s390/include/asm/eadm.h

File Facts

System

Linux kernel

Corpus path

arch/s390/include/asm/eadm.h

Extension

.h

Size

2116 bytes

Lines

122

Domain

Architecture Layer

Bucket

arch/s390

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
• linux/device.h
• linux/blk_types.h
• asm/dma-types.h

Detected Declarations

• struct arqb
• struct arsb
• struct msb
• struct aidaw
• struct aob
• struct aob_rq_header
• struct scm_device
• struct scm_driver
• enum scm_event

Annotated Snippet

struct device_driver drv;
	int (*probe) (struct scm_device *scmdev);
	void (*remove) (struct scm_device *scmdev);
	void (*notify) (struct scm_device *scmdev, enum scm_event event);
	void (*handler) (struct scm_device *scmdev, void *data,
			blk_status_t error);
};

int scm_driver_register(struct scm_driver *scmdrv);
void scm_driver_unregister(struct scm_driver *scmdrv);

int eadm_start_aob(struct aob *aob);
void scm_irq_handler(struct aob *aob, blk_status_t error);

#endif /* _ASM_S390_EADM_H */

Annotation

• Immediate include surface: `linux/types.h`, `linux/device.h`, `linux/blk_types.h`, `asm/dma-types.h`.
• Detected declarations: `struct arqb`, `struct arsb`, `struct msb`, `struct aidaw`, `struct aob`, `struct aob_rq_header`, `struct scm_device`, `struct scm_driver`, `enum scm_event`.
• Atlas domain: Architecture Layer / arch/s390.
• 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.