drivers/hv/mshv.h
Source file repositories/reference/linux-study-clean/drivers/hv/mshv.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/hv/mshv.h- Extension
.h- Size
- 775 bytes
- Lines
- 29
- Domain
- Driver Families
- Bucket
- drivers/hv
- Inferred role
- Driver Families: implementation source
- Status
- source implementation candidate
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/stddef.hlinux/string.hhyperv/hvhdk.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef _MSHV_H_
#define _MSHV_H_
#include <linux/stddef.h>
#include <linux/string.h>
#include <hyperv/hvhdk.h>
#define mshv_field_nonzero(STRUCT, MEMBER) \
memchr_inv(&((STRUCT).MEMBER), \
0, sizeof_field(typeof(STRUCT), MEMBER))
int hv_call_get_vp_registers(u32 vp_index, u64 partition_id, u16 count,
union hv_input_vtl input_vtl,
struct hv_register_assoc *registers);
int hv_call_set_vp_registers(u32 vp_index, u64 partition_id, u16 count,
union hv_input_vtl input_vtl,
struct hv_register_assoc *registers);
int hv_call_get_partition_property(u64 partition_id, u64 property_code,
u64 *property_value);
#endif /* _MSHV_H */
Annotation
- Immediate include surface: `linux/stddef.h`, `linux/string.h`, `hyperv/hvhdk.h`.
- Atlas domain: Driver Families / drivers/hv.
- 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.