arch/s390/hypfs/hypfs_vm.h

File Facts

System

Linux kernel

Corpus path

arch/s390/hypfs/hypfs_vm.h

Extension

.h

Size

1007 bytes

Lines

51

Domain

Architecture Layer

Bucket

arch/s390

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 diag2fc_data
• struct diag2fc_parm_list

Annotated Snippet

struct diag2fc_data {
	__u32 version;
	__u32 flags;
	__u64 used_cpu;
	__u64 el_time;
	__u64 mem_min_kb;
	__u64 mem_max_kb;
	__u64 mem_share_kb;
	__u64 mem_used_kb;
	__u32 pcpus;
	__u32 lcpus;
	__u32 vcpus;
	__u32 ocpus;
	__u32 cpu_max;
	__u32 cpu_shares;
	__u32 cpu_use_samp;
	__u32 cpu_delay_samp;
	__u32 page_wait_samp;
	__u32 idle_samp;
	__u32 other_samp;
	__u32 total_samp;
	char  guest_name[DIAG2FC_NAME_LEN];
};

struct diag2fc_parm_list {
	char userid[DIAG2FC_NAME_LEN];
	char aci_grp[DIAG2FC_NAME_LEN];
	__u64 addr;
	__u32 size;
	__u32 fmt;
};

void *diag2fc_store(char *query, unsigned int *count, int offset);
void diag2fc_free(const void *data);
extern char *diag2fc_guest_query;

#endif /* _S390_HYPFS_VM_H_ */

Annotation

• Detected declarations: `struct diag2fc_data`, `struct diag2fc_parm_list`.
• Atlas domain: Architecture Layer / arch/s390.
• 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.