drivers/net/ethernet/mellanox/mlx5/core/lib/hv.h

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/mellanox/mlx5/core/lib/hv.h

Extension

.h

Size

667 bytes

Lines

23

Domain

Driver Families

Bucket

drivers/net

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/hyperv.h
• linux/mlx5/driver.h

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#ifndef __LIB_HV_H__
#define __LIB_HV_H__

#if IS_ENABLED(CONFIG_PCI_HYPERV_INTERFACE)

#include <linux/hyperv.h>
#include <linux/mlx5/driver.h>

int mlx5_hv_read_config(struct mlx5_core_dev *dev, void *buf, int len,
			int offset);
int mlx5_hv_write_config(struct mlx5_core_dev *dev, void *buf, int len,
			 int offset);
int mlx5_hv_register_invalidate(struct mlx5_core_dev *dev, void *context,
				void (*block_invalidate)(void *context,
							 u64 block_mask));
void mlx5_hv_unregister_invalidate(struct mlx5_core_dev *dev);
#endif

#endif /* __LIB_HV_H__ */

Annotation

• Immediate include surface: `linux/hyperv.h`, `linux/mlx5/driver.h`.
• Atlas domain: Driver Families / drivers/net.
• 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.