arch/s390/kernel/diag/diag_misc.c

File Facts

System

Linux kernel

Corpus path

arch/s390/kernel/diag/diag_misc.c

Extension

.c

Size

1185 bytes

Lines

64

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/fs.h
• linux/init.h
• linux/ioctl.h
• linux/kernel.h
• linux/miscdevice.h
• linux/types.h
• uapi/asm/diag.h
• diag_ioctl.h

Detected Declarations

• function diag_ioctl
• function diag_init
• module init diag_init

Annotated Snippet

static const struct file_operations fops = {
	.owner		= THIS_MODULE,
	.open		= nonseekable_open,
	.unlocked_ioctl	= diag_ioctl,
};

static struct miscdevice diagdev = {
	.name	= "diag",
	.minor	= MISC_DYNAMIC_MINOR,
	.fops	= &fops,
	.mode	= 0444,
};

static int diag_init(void)
{
	return misc_register(&diagdev);
}

device_initcall(diag_init);

Annotation

• Immediate include surface: `linux/fs.h`, `linux/init.h`, `linux/ioctl.h`, `linux/kernel.h`, `linux/miscdevice.h`, `linux/types.h`, `uapi/asm/diag.h`, `diag_ioctl.h`.
• Detected declarations: `function diag_ioctl`, `function diag_init`, `module init diag_init`.
• 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.