arch/arm64/kvm/hyp/nvhe/events.c

File Facts

System

Linux kernel

Corpus path

arch/arm64/kvm/hyp/nvhe/events.c

Extension

.c

Size

536 bytes

Lines

26

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

• nvhe/mm.h
• nvhe/trace.h
• nvhe/define_events.h

Detected Declarations

• function Copyright

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0-only
/*
 * Copyright (C) 2025 Google LLC
 * Author: Vincent Donnefort <vdonnefort@google.com>
 */

#include <nvhe/mm.h>
#include <nvhe/trace.h>

#include <nvhe/define_events.h>

int __tracing_enable_event(unsigned short id, bool enable)
{
	struct hyp_event_id *event_id = &__hyp_event_ids_start[id];
	atomic_t *enabled;

	if (event_id >= __hyp_event_ids_end)
		return -EINVAL;

	enabled = hyp_fixmap_map(__hyp_pa(&event_id->enabled));
	atomic_set(enabled, enable);
	hyp_fixmap_unmap();

	return 0;
}

Annotation

• Immediate include surface: `nvhe/mm.h`, `nvhe/trace.h`, `nvhe/define_events.h`.
• Detected declarations: `function Copyright`.
• 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.