arch/parisc/kernel/perf_event.c
Source file repositories/reference/linux-study-clean/arch/parisc/kernel/perf_event.c
File Facts
- System
- Linux kernel
- Corpus path
arch/parisc/kernel/perf_event.c- Extension
.c- Size
- 569 bytes
- Lines
- 28
- Domain
- Architecture Layer
- Bucket
- arch/parisc
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/kernel.hlinux/perf_event.hasm/unwind.h
Detected Declarations
function Copyright
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
/*
* Performance event support for parisc
*
* Copyright (C) 2025 by Helge Deller <deller@gmx.de>
*/
#include <linux/kernel.h>
#include <linux/perf_event.h>
#include <asm/unwind.h>
void perf_callchain_kernel(struct perf_callchain_entry_ctx *entry,
struct pt_regs *regs)
{
struct unwind_frame_info info;
unwind_frame_init_task(&info, current, NULL);
while (1) {
if (unwind_once(&info) < 0 || info.ip == 0)
break;
if (!__kernel_text_address(info.ip) ||
perf_callchain_store(entry, info.ip))
return;
}
}
Annotation
- Immediate include surface: `linux/kernel.h`, `linux/perf_event.h`, `asm/unwind.h`.
- Detected declarations: `function Copyright`.
- Atlas domain: Architecture Layer / arch/parisc.
- 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.