arch/mips/include/asm/ftrace.h

File Facts

System

Linux kernel

Corpus path

arch/mips/include/asm/ftrace.h

Extension

.h

Size

2771 bytes

Lines

111

Domain

Architecture Layer

Bucket

arch/mips

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

• No C-style include directives detected by the generator.

Detected Declarations

• struct dyn_arch_ftrace
• function ftrace_call_adjust
• function arch_syscall_match_sym_name

Annotated Snippet

struct dyn_arch_ftrace {
};

#endif /*  CONFIG_DYNAMIC_FTRACE */

void prepare_ftrace_return(unsigned long *parent_ra_addr, unsigned long self_ra,
			   unsigned long fp);

#endif /* __ASSEMBLER__ */
#endif /* CONFIG_FUNCTION_TRACER */

#ifdef CONFIG_FTRACE_SYSCALLS
#ifndef __ASSEMBLER__
/*
 * Some syscall entry functions on mips start with "__sys_" (fork and clone,
 * for instance). We should also match the sys_ variant with those.
 */
#define ARCH_HAS_SYSCALL_MATCH_SYM_NAME
static inline bool arch_syscall_match_sym_name(const char *sym,
					       const char *name)
{
	return !strcmp(sym, name) ||
		(!strncmp(sym, "__sys_", 6) && !strcmp(sym + 6, name + 4));
}
#endif /* __ASSEMBLER__ */
#endif /* CONFIG_FTRACE_SYSCALLS */
#endif /* _ASM_MIPS_FTRACE_H */

Annotation

• Detected declarations: `struct dyn_arch_ftrace`, `function ftrace_call_adjust`, `function arch_syscall_match_sym_name`.
• Atlas domain: Architecture Layer / arch/mips.
• 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.