arch/s390/hypfs/hypfs.h
Source file repositories/reference/linux-study-clean/arch/s390/hypfs/hypfs.h
File Facts
- System
- Linux kernel
- Corpus path
arch/s390/hypfs/hypfs.h- Extension
.h- Size
- 1985 bytes
- Lines
- 83
- 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
linux/fs.hlinux/types.hlinux/debugfs.hlinux/workqueue.hlinux/kref.hasm/hypfs.h
Detected Declarations
struct hypfs_dbfs_filestruct hypfs_dbfs_datastruct hypfs_dbfs_filefunction hypfs_fs_init
Annotated Snippet
struct hypfs_dbfs_data {
void *buf;
void *buf_free_ptr;
size_t size;
struct hypfs_dbfs_file *dbfs_file;
};
struct hypfs_dbfs_file {
const char *name;
int (*data_create)(void **data, void **data_free_ptr,
size_t *size);
void (*data_free)(const void *buf_free_ptr);
long (*unlocked_ioctl) (struct file *, unsigned int,
unsigned long);
/* Private data for hypfs_dbfs.c */
struct mutex lock;
struct dentry *dentry;
};
extern void hypfs_dbfs_create_file(struct hypfs_dbfs_file *df);
extern void hypfs_dbfs_remove_file(struct hypfs_dbfs_file *df);
#endif /* _HYPFS_H_ */
Annotation
- Immediate include surface: `linux/fs.h`, `linux/types.h`, `linux/debugfs.h`, `linux/workqueue.h`, `linux/kref.h`, `asm/hypfs.h`.
- Detected declarations: `struct hypfs_dbfs_file`, `struct hypfs_dbfs_data`, `struct hypfs_dbfs_file`, `function hypfs_fs_init`.
- 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.