include/linux/mlx5/mlx5_ifc_vdpa.h

File Facts

System

Linux kernel

Corpus path

include/linux/mlx5/mlx5_ifc_vdpa.h

Extension

.h

Size

5747 bytes

Lines

227

Domain

Core OS

Bucket

Core Kernel Interface

Inferred role

Core OS: implementation source

Status

source implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• 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 mlx5_ifc_virtio_q_bits
• struct mlx5_ifc_virtio_net_q_object_bits
• struct mlx5_ifc_create_virtio_net_q_in_bits
• struct mlx5_ifc_create_virtio_net_q_out_bits
• struct mlx5_ifc_destroy_virtio_net_q_in_bits
• struct mlx5_ifc_destroy_virtio_net_q_out_bits
• struct mlx5_ifc_query_virtio_net_q_in_bits
• struct mlx5_ifc_query_virtio_net_q_out_bits
• struct mlx5_ifc_modify_virtio_net_q_in_bits
• struct mlx5_ifc_modify_virtio_net_q_out_bits
• struct mlx5_ifc_virtio_q_counters_bits
• struct mlx5_ifc_create_virtio_q_counters_in_bits
• struct mlx5_ifc_create_virtio_q_counters_out_bits
• struct mlx5_ifc_destroy_virtio_q_counters_in_bits
• struct mlx5_ifc_destroy_virtio_q_counters_out_bits
• struct mlx5_ifc_query_virtio_q_counters_in_bits
• struct mlx5_ifc_query_virtio_q_counters_out_bits

Annotated Snippet

struct mlx5_ifc_virtio_q_bits {
	u8    virtio_q_type[0x8];
	u8    reserved_at_8[0x5];
	u8    event_mode[0x3];
	u8    queue_index[0x10];

	u8    full_emulation[0x1];
	u8    virtio_version_1_0[0x1];
	u8    reserved_at_22[0x2];
	u8    offload_type[0x4];
	u8    event_qpn_or_msix[0x18];

	u8    doorbell_stride_index[0x10];
	u8    queue_size[0x10];

	u8    device_emulation_id[0x20];

	u8    desc_addr[0x40];

	u8    used_addr[0x40];

	u8    available_addr[0x40];

	u8    virtio_q_mkey[0x20];

	u8    max_tunnel_desc[0x10];
	u8    reserved_at_170[0x8];
	u8    error_type[0x8];

	u8    umem_1_id[0x20];

	u8    umem_1_size[0x20];

	u8    umem_1_offset[0x40];

	u8    umem_2_id[0x20];

	u8    umem_2_size[0x20];

	u8    umem_2_offset[0x40];

	u8    umem_3_id[0x20];

	u8    umem_3_size[0x20];

	u8    umem_3_offset[0x40];

	u8    counter_set_id[0x20];

	u8    reserved_at_320[0x8];
	u8    pd[0x18];

	u8    reserved_at_340[0x20];

	u8    desc_group_mkey[0x20];

	u8    reserved_at_380[0x80];
};

struct mlx5_ifc_virtio_net_q_object_bits {
	u8    modify_field_select[0x40];

	u8    reserved_at_40[0x20];

	u8    vhca_id[0x10];
	u8    reserved_at_70[0x10];

	u8    queue_feature_bit_mask_12_3[0xa];
	u8    dirty_bitmap_dump_enable[0x1];
	u8    vhost_log_page[0x5];
	u8    reserved_at_90[0xc];
	u8    state[0x4];

	u8    reserved_at_a0[0x5];
	u8    queue_feature_bit_mask_2_0[0x3];
	u8    tisn_or_qpn[0x18];

	u8    dirty_bitmap_mkey[0x20];

	u8    dirty_bitmap_size[0x20];

	u8    dirty_bitmap_addr[0x40];

	u8    hw_available_index[0x10];
	u8    hw_used_index[0x10];

	u8    reserved_at_160[0xa0];

	struct mlx5_ifc_virtio_q_bits virtio_q_context;
};

Annotation

• Detected declarations: `struct mlx5_ifc_virtio_q_bits`, `struct mlx5_ifc_virtio_net_q_object_bits`, `struct mlx5_ifc_create_virtio_net_q_in_bits`, `struct mlx5_ifc_create_virtio_net_q_out_bits`, `struct mlx5_ifc_destroy_virtio_net_q_in_bits`, `struct mlx5_ifc_destroy_virtio_net_q_out_bits`, `struct mlx5_ifc_query_virtio_net_q_in_bits`, `struct mlx5_ifc_query_virtio_net_q_out_bits`, `struct mlx5_ifc_modify_virtio_net_q_in_bits`, `struct mlx5_ifc_modify_virtio_net_q_out_bits`.
• Atlas domain: Core OS / Core Kernel Interface.
• Implementation status: source implementation candidate.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.