drivers/infiniband/hw/hfi1/trace.h

File Facts

System

Linux kernel

Corpus path

drivers/infiniband/hw/hfi1/trace.h

Extension

.h

Size

709 bytes

Lines

25

Domain

Driver Families

Bucket

drivers/infiniband

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.

Dependency Surface

• trace_dbg.h
• trace_misc.h
• trace_ctxts.h
• trace_ibhdrs.h
• trace_rc.h
• trace_rx.h
• trace_tx.h
• trace_mmu.h
• trace_iowait.h
• trace_tid.h

Detected Declarations

• function Copyright

Annotated Snippet

#define packettype_name(etype) { RHF_RCV_TYPE_##etype, #etype }
#define show_packettype(etype)                  \
__print_symbolic(etype,                         \
	packettype_name(EXPECTED),              \
	packettype_name(EAGER),                 \
	packettype_name(IB),                    \
	packettype_name(ERROR),                 \
	packettype_name(BYPASS))

#include "trace_dbg.h"
#include "trace_misc.h"
#include "trace_ctxts.h"
#include "trace_ibhdrs.h"
#include "trace_rc.h"
#include "trace_rx.h"
#include "trace_tx.h"
#include "trace_mmu.h"
#include "trace_iowait.h"
#include "trace_tid.h"

Annotation

• Immediate include surface: `trace_dbg.h`, `trace_misc.h`, `trace_ctxts.h`, `trace_ibhdrs.h`, `trace_rc.h`, `trace_rx.h`, `trace_tx.h`, `trace_mmu.h`.
• Detected declarations: `function Copyright`.
• Atlas domain: Driver Families / drivers/infiniband.
• 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.