arch/arm64/include/asm/kvm_hyptrace.h

File Facts

System

Linux kernel

Corpus path

arch/arm64/include/asm/kvm_hyptrace.h

Extension

.h

Size

605 bytes

Lines

27

Domain

Architecture Layer

Bucket

arch/arm64

Inferred role

Architecture Layer: implementation source

Status

source implementation candidate

Why This File Exists

CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.

• CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/ring_buffer.h

Detected Declarations

• struct hyp_trace_desc
• struct hyp_event_id

Annotated Snippet

struct hyp_trace_desc {
	unsigned long			bpages_backing_start;
	size_t				bpages_backing_size;
	struct trace_buffer_desc	trace_buffer_desc;

};

struct hyp_event_id {
	unsigned short	id;
	atomic_t	enabled;
};

extern struct remote_event __hyp_events_start[];
extern struct remote_event __hyp_events_end[];

/* hyp_event section used by the hypervisor */
extern struct hyp_event_id __hyp_event_ids_start[];
extern struct hyp_event_id __hyp_event_ids_end[];

#endif

Annotation

• Immediate include surface: `linux/ring_buffer.h`.
• Detected declarations: `struct hyp_trace_desc`, `struct hyp_event_id`.
• Atlas domain: Architecture Layer / arch/arm64.
• Implementation status: source implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.