drivers/net/ethernet/google/gve/gve_register.h

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/google/gve/gve_register.h

Extension

.h

Size

896 bytes

Lines

38

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

• No C-style include directives detected by the generator.

Detected Declarations

• struct gve_registers
• enum gve_device_status_flags
• enum gve_driver_status_flags

Annotated Snippet

struct gve_registers {
	__be32	device_status;
	__be32	driver_status;
	__be32	max_tx_queues;
	__be32	max_rx_queues;
	__be32	adminq_pfn;
	__be32	adminq_doorbell;
	__be32	adminq_event_counter;
	u8	reserved[3];
	u8	driver_version;
	__be32	adminq_base_address_hi;
	__be32	adminq_base_address_lo;
	__be16	adminq_length;
};

enum gve_device_status_flags {
	GVE_DEVICE_STATUS_RESET_MASK		= BIT(1),
	GVE_DEVICE_STATUS_LINK_STATUS_MASK	= BIT(2),
	GVE_DEVICE_STATUS_REPORT_STATS_MASK	= BIT(3),
	GVE_DEVICE_STATUS_DEVICE_IS_RESET	= BIT(4),
};

enum gve_driver_status_flags {
	GVE_DRIVER_STATUS_RUN_MASK		= BIT(0),
	GVE_DRIVER_STATUS_RESET_MASK		= BIT(1),
};
#endif /* _GVE_REGISTER_H_ */

Annotation

• Detected declarations: `struct gve_registers`, `enum gve_device_status_flags`, `enum gve_driver_status_flags`.
• 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.