include/linux/trace_remote_event.h

File Facts

System

Linux kernel

Corpus path

include/linux/trace_remote_event.h

Extension

.h

Size

744 bytes

Lines

34

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.
• 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 trace_remote
• struct trace_event_fields
• struct trace_seq
• struct remote_event_hdr
• struct remote_event

Annotated Snippet

struct remote_event_hdr {
	unsigned short	id;
};

#define REMOTE_EVENT_NAME_MAX 30
struct remote_event {
	char				name[REMOTE_EVENT_NAME_MAX];
	unsigned short			id;
	bool				enabled;
	struct trace_remote		*remote;
	struct trace_event_fields	*fields;
	char				*print_fmt;
	void				(*print)(void *evt, struct trace_seq *seq);
};

#define RE_STRUCT(__args...) __args
#define re_field(__type, __field) __type __field;

#define REMOTE_EVENT_FORMAT(__name, __struct)	\
	struct remote_event_format_##__name {	\
		struct remote_event_hdr hdr;	\
		__struct			\
	}
#endif

Annotation

• Detected declarations: `struct trace_remote`, `struct trace_event_fields`, `struct trace_seq`, `struct remote_event_hdr`, `struct remote_event`.
• Atlas domain: Core OS / Core Kernel Interface.
• 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.