tools/perf/arch/arm/tests/vectors-page.c

File Facts

System

Linux kernel

Corpus path

tools/perf/arch/arm/tests/vectors-page.c

Extension

.c

Size

564 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

• stdio.h
• string.h
• linux/compiler.h
• debug.h
• tests/tests.h
• util/find-map.c

Detected Declarations

• function test__vectors_page

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0
#include <stdio.h>
#include <string.h>
#include <linux/compiler.h>

#include "debug.h"
#include "tests/tests.h"
#include "util/find-map.c"

#define VECTORS__MAP_NAME "[vectors]"

static int test__vectors_page(struct test_suite *test __maybe_unused, int subtest __maybe_unused)
{
	void *start, *end;

	if (find_map(&start, &end, VECTORS__MAP_NAME)) {
		pr_err("%s not found, is CONFIG_KUSER_HELPERS enabled?\n",
		       VECTORS__MAP_NAME);
		return TEST_FAIL;
	}

	return TEST_OK;
}

DEFINE_SUITE("Vectors page", vectors_page);

Annotation

• Immediate include surface: `stdio.h`, `string.h`, `linux/compiler.h`, `debug.h`, `tests/tests.h`, `util/find-map.c`.
• Detected declarations: `function test__vectors_page`.
• 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.