tools/tracing/rtla/tests/bpf/bpf_action_map.c

File Facts

System

Linux kernel

Corpus path

tools/tracing/rtla/tests/bpf/bpf_action_map.c

Extension

.c

Size

561 bytes

Lines

26

Domain

Support Tooling And Documentation

Bucket

tools

Inferred role

Support Tooling And Documentation: implementation source

Status

source implementation candidate

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

• Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/bpf.h
• bpf/bpf_tracing.h

Detected Declarations

• struct trace_event_raw_timerlat_sample
• function action_handler

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0
#include <linux/bpf.h>
#include <bpf/bpf_tracing.h>

char LICENSE[] SEC("license") = "GPL";

struct {
	__uint(type, BPF_MAP_TYPE_ARRAY);
	__uint(max_entries, 1);
	__type(key, unsigned int);
	__type(value, unsigned long long);
} rtla_test_map SEC(".maps");

struct trace_event_raw_timerlat_sample;

SEC("tp/timerlat_action")
int action_handler(struct trace_event_raw_timerlat_sample *tp_args)
{
	unsigned int key = 0;
	unsigned long long value = 42;

	bpf_map_update_elem(&rtla_test_map, &key, &value, BPF_ANY);

	return 0;
}

Annotation

• Immediate include surface: `linux/bpf.h`, `bpf/bpf_tracing.h`.
• Detected declarations: `struct trace_event_raw_timerlat_sample`, `function action_handler`.
• Atlas domain: Support Tooling And Documentation / tools.
• 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.